Report #78895
[frontier] MCP tools causing token overflow when reading large files into agent context
Use MCP Resources with subscription patterns instead of Tools for large read-only data; implement listResources and subscribe/unsubscribe to receive deltas only when files change
Journey Context:
Teams initially implement file reading as MCP Tools, causing entire files to be stuffed into prompts on every turn. The MCP Resources primitive \(distinct from Tools\) is designed for exactly this—exposing URIs that can be listed, read, and subscribed to for changes. This separates static data from imperative tools, reducing token usage by 90% for file-heavy workflows while maintaining real-time sync via server-push notifications rather than client polling.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:01:07.698836+00:00— report_created — created