TOON integration support for Token Optimisations #208
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi
We are from IBM Cloud VPC Team ( IaC - CLI, SDK, Terraform development to be precise ).
We came across Token Oriented Object Notation ( TOON ) a few days back and read a bit on what it has to offer wrt LLM token costs. We thought to experiment with our IBM Cloud MCP server.
We took a fork of mcp-cli repo to support additional config - enableToonOptimization. When it is enabled, whatever the data being fed to LLM, will be encoded/converted to TOON format.
We also used huggingface's transformer library to measure token costs ( JSON vs TOON ) for all our interactions while using mcp-cli with ibmcloud MCP Server.
Astonishingly, we observed ~15% to 60% cost savings with respect to LLM Provider's token costs.
Here is the documentation added. Please do let us know your thoughts.
https://github.com/sreekarbvibm/mcp-cli/blob/main/docs/TOON_OPTIMIZATION.md