You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if section 5.2.6 is leading to some token bloat. I can see why it was important earlier to include JSON in textcontent for backwards compatibility. But, leaving this in the specification permanently can increase payload sizes significantly. Even going from SHOULD to COULD may help.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Model Context Protocol
Uh oh!
There was an error while loading. Please reload this page.
-
I wonder if section 5.2.6 is leading to some token bloat. I can see why it was important earlier to include JSON in textcontent for backwards compatibility. But, leaving this in the specification permanently can increase payload sizes significantly. Even going from SHOULD to COULD may help.
https://modelcontextprotocol.io/specification/2025-06-18/server/tools#structured-content
"For backwards compatibility, a tool that returns structured content SHOULD also return the serialized JSON in a TextContent block."
Beta Was this translation helpful? Give feedback.
All reactions