How does it work? Im building a video editor and right now it has access to nearly 100 tools. Would be good to learn the techniques you used to make tool discovery more efficient.

I don’t think the Show Me section makes sense, the TOON variant clearly doesn’t have the same information. And the examples in the “How TOON works” section focuses on number of characters instead of tokens. I would think “null” is a single token anyway, why bother replacing it with an uncommon character?

I really doubt that null and \n make any sense to replace with non ascii symbols. They are both most likely already a token only and for other purposes at least \n becomes larger as a symbol.

Sorry, isnt this just compression? Lookups burn tokens just on the other end?

I am not going to trust a single number thrown by these AI hustlers written in that salesman voice.

Leave alone 97%.

> Your agent calls 20 tools. Each returns 500-3,000 tokens wrapped in {"content":[{"type":"text","text":"..."}]}.

This is a problem with your tool design. Most MCPs are fully vibe coded without any thought about tool selection.

> On a 128K context window, that's 30-55% gone. Not on work. On syntax.

Tool output is not "syntax" you donkey clanker.

Again, use the code approach, let the LLM filter out the JSON using tools. This TOON thing is just vibes. Most of the time your tool output should not even be JSON. It should be well formatted markdown. In cases where it's large structured data, your LLM should have tools (code / jq) to dissect it. So TOON is pointless.