Upon checking the server logs the call also never arrives at the destination server. Furthermore, the message "not all arguments converted during string formatting" is a python error, where the target server is implemented in .net. When loading the json with an invalid API Server address, the validation succeeds and the same error occurs when running the tool.
Additionally, as the screenshot shows, the error message is given with the request JSON, the response JSON actually looks different. So i guess there is some problem with sending JSON as POST body?
Steps to Reproduce
Upload the v3schemaswagger.json somewhere where it can be accessed via HTTP from the OWUI instance
use that url to load a tool in Adminpanel > Settings > Tools > Add Connection
Activate that tool in a chat and ask about your todos
This looks kind of fishy to me in the browser output, but maybe thats intended (arguments=""{}"", having quotes inside the arguments). Could not find that in the server logs tho
Originally created by @Jenscaasen on GitHub (May 22, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
0.6.10
### Ollama Version (if applicable)
_No response_
### Operating System
Linux Mint
### Browser (if applicable)
Firefox
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have listed steps to reproduce the bug in detail.
### Expected Behavior
Adding a Toolserver with OpenAPI v3 definition > Using Tool > Tool can be used
[v3schemaswagger.json](https://github.com/user-attachments/files/20394278/v3schemaswagger.json)
Check with POSTMAN:
POST https://server/api/restcalls/b594cd8c-d580-4073-8731-e1119a628425
Body: {}
works


Other openapi tools use that definition successfully as well.
Connection verifies (no cors problem):

### Actual Behavior
Adding a Toolserver with OpenAPI v3 definition > Using Tool >
[log.txt](https://github.com/user-attachments/files/20393805/log.txt)
(can not share more logs)

Upon checking the server logs the call also never arrives at the destination server. Furthermore, the message "not all arguments converted during string formatting" is a python error, where the target server is implemented in .net. When loading the json with an invalid API Server address, the validation succeeds and the same error occurs when running the tool.
Additionally, as the screenshot shows, the error message is given with the request JSON, the response JSON actually looks different. So i guess there is some problem with sending JSON as POST body?
### Steps to Reproduce
1. Upload the v3schemaswagger.json somewhere where it can be accessed via HTTP from the OWUI instance
2. use that url to load a tool in Adminpanel > Settings > Tools > Add Connection
3. Activate that tool in a chat and ask about your todos
### Logs & Screenshots
added above
also more browser logs:
[console-export-2025-5-22_16-43-29.txt](https://github.com/user-attachments/files/20394648/console-export-2025-5-22_16-43-29.txt)
### Additional Information

This looks kind of fishy to me in the browser output, but maybe thats intended (arguments=""{}"", having quotes inside the arguments). Could not find that in the server logs tho
GiteaMirror
added the bug label 2025-11-11 16:16:09 -06:00
I'm guessing this is accessed via Direct Tools, I'd highly suggest you check your network tab to see whether the webui is making a correct network request.
@tjbck commented on GitHub (May 22, 2025):
I'm guessing this is accessed via Direct Tools, I'd highly suggest you check your network tab to see whether the webui is making a correct network request.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Jenscaasen on GitHub (May 22, 2025).
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.10
Ollama Version (if applicable)
No response
Operating System
Linux Mint
Browser (if applicable)
Firefox
Confirmation
README.md.Expected Behavior
Adding a Toolserver with OpenAPI v3 definition > Using Tool > Tool can be used
v3schemaswagger.json
Check with POSTMAN:
POST https://server/api/restcalls/b594cd8c-d580-4073-8731-e1119a628425
Body: {}
works
Other openapi tools use that definition successfully as well.
Connection verifies (no cors problem):

Actual Behavior
Adding a Toolserver with OpenAPI v3 definition > Using Tool >
log.txt

(can not share more logs)
Upon checking the server logs the call also never arrives at the destination server. Furthermore, the message "not all arguments converted during string formatting" is a python error, where the target server is implemented in .net. When loading the json with an invalid API Server address, the validation succeeds and the same error occurs when running the tool.
Additionally, as the screenshot shows, the error message is given with the request JSON, the response JSON actually looks different. So i guess there is some problem with sending JSON as POST body?
Steps to Reproduce
Logs & Screenshots
added above
also more browser logs:
console-export-2025-5-22_16-43-29.txt
Additional Information
This looks kind of fishy to me in the browser output, but maybe thats intended (arguments=""{}"", having quotes inside the arguments). Could not find that in the server logs tho
@tjbck commented on GitHub (May 22, 2025):
I'm guessing this is accessed via Direct Tools, I'd highly suggest you check your network tab to see whether the webui is making a correct network request.