Reduce noisy MCP missing-capability reports

[masnwilliams]

summary

• tell agents to report only genuine server capability gaps after checking available tools
• exclude existing fallbacks, transient failures, capacity limits, and client-side permission restrictions
• cover the updated tool contract in the MCP analytics integration test

why

The previous description explicitly encouraged reports even when an existing tool could complete the task. That inflated missing-capability analytics with fallback, capacity, and client-policy issues.

testing

• bun test
• bun test src/lib/mcp/analytics.test.ts
• bunx prettier --check src/lib/mcp/analytics.ts src/lib/mcp/analytics.test.ts

bun run format:check still reports the pre-existing AGENTS.md formatting warning.

---

Note

Low Risk
Copy-only change to an MCP tool description plus test assertions; no runtime logic or analytics pipeline changes.

Overview
Tightens agent guidance for the get_more_tools missing-capability MCP tool so $mcp_missing_capability analytics reflect real server gaps instead of fallback use, transient errors, capacity limits, or client permission blocks.

The tool description in registerMissingCapabilityTool no longer nudges agents to report when existing tools might work. It now requires checking listed tools first and directs agents to use those tools or submit_feedback for the excluded cases.

The MCP analytics integration test is renamed and extended to assert the published get_more_tools description includes the new contract language.

^{Reviewed by Cursor Bugbot for commit 63efe4c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
mcp	Ready	Preview	Aug 31, 2026 9:22pm