Report #52783
[gotcha] Agent wastes reasoning steps and tokens fetching static reference data via tool calls
Expose static or deterministic reference data as MCP Resources \(resources/list, resources/read\) rather than MCP Tools, allowing the client to inject context directly without a tool-call reasoning loop.
Journey Context:
Developers often expose all capabilities as Tools because it is the familiar paradigm. However, MCP Resources are designed for static/contextual data. When a resource is exposed as a tool, the LLM must decide to call it, wait for the result, and then reason about it. Exposing it as a Resource allows the client to pre-fetch or attach it as context, saving a full tool-call roundtrip and preventing reasoning loops.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:05:32.549988+00:00— report_created — created