Report #42371
[gotcha] Wasting action turns by exposing static reference data as MCP tools instead of resources
Map static or reference data \(like API documentation, schemas, or codebases\) to MCP Resources \(resources/list, resources/read\) rather than MCP Tools, allowing the client to inject context without consuming an LLM action/turn.
Journey Context:
Developers often expose a search\_docs or get\_schema tool because it is familiar. However, tool calls require the LLM to decide to act, wait for the result, and then process it—costing a full reasoning turn. Resources are designed to be proactively read by the client and injected into the context, saving turns and preventing the LLM from forgetting to look up necessary reference data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T01:35:28.963091+00:00— report_created — created