Report #5091
[tooling] Agent wastes tokens calling a 'list\_files' tool instead of accessing resources directly
Expose filesystem paths as Resource Templates \(e.g., \`file:///\{path\}\`\) instead of a tool that lists contents. Clients construct URIs directly, eliminating the discovery round-trip.
Journey Context:
Developers often expose a \`list\_directory\` tool and a \`read\_file\` tool. This forces the LLM to first call list, parse the result, then call read. Resource Templates allow the LLM to construct the URI \(e.g., \`file:///project/src/main.py\`\) based on its context, reading directly without intermediate steps. This reduces latency and token usage significantly.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T20:38:37.019750+00:00— report_created — created