[GH-ISSUE #18454] feat: Add YAML support in tool servers to reduce total conversation tokens #34131

Closed
opened 2026-04-25 08:03:38 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @MordiSacks on GitHub (Oct 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18454

Check Existing Issues

  • I have searched all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Problem Description

Tool server integration does not support YAML

Desired Solution you'd like

Support YAML

Alternatives Considered

No response

Additional Context

Currently using tool servers relays on JSON for request/response, while JSON is easy and very mainstream, YAML is much more compact, I propose adding support for YAML request/response or at very least just response, in my case I have a payload that was 4773 chars in JSON and only 1253 in YAML, this can have a huge impact on token usage.

Originally created by @MordiSacks on GitHub (Oct 20, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18454 ### Check Existing Issues - [x] I have searched all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request. ### Problem Description Tool server integration does not support YAML ### Desired Solution you'd like Support YAML ### Alternatives Considered _No response_ ### Additional Context Currently using tool servers relays on JSON for request/response, while JSON is easy and very mainstream, YAML is much more compact, I propose adding support for YAML request/response or at very least just response, in my case I have a payload that was 4773 chars in JSON and only 1253 in YAML, this can have a huge impact on token usage.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#34131