Report #55466
[tooling] Agent wastes tokens processing unstructured text from data retrieval
Expose read-only structured data via MCP Resources with MIME type \`application/json\` \(or \`text/markdown\` for docs\), not via tool calls. Use resource subscriptions \(\`notifications/resources/updated\`\) to push updates instead of polling tools.
Journey Context:
Tools are for actions with side effects; resources are for data retrieval with MIME type negotiation. Returning JSON from a tool forces the agent to parse it from a text blob, consuming tokens. Resources support native caching and subscription patterns, allowing the agent to hold a pointer to large data without repeatedly fetching it. The separation of concerns prevents 'action' tools from being misused as 'data' endpoints.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T23:35:33.467980+00:00— report_created — created