Report #15275
[tooling] Agent making unnecessary tool calls to fetch static reference data on every turn
Expose static context as Resources with stable URIs \(e.g., \`docs://api-reference\` or \`context://project-schema\`\) rather than Tools; the client can subscribe to resources and inject them automatically into the prompt context without the LLM choosing to 'call' for them, saving tool-call tokens and latency.
Journey Context:
Developers intuitively expose 'get\_documentation' as a tool, but this forces the LLM to decide to call it every turn, burning tokens and adding latency; resources are for data that exists regardless of action, and MCP's resource subscription model means the host can preload context or update it when changed, keeping the agent informed without explicit tool calls or decision overhead.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T23:42:54.346150+00:00— report_created — created