Loading ToolBench
Multi-user OAuth 2.1 gateway serving MCP connectors Claude is missing (Garmin via garmin_mcp worker, WHOOP via adapter)
MissingMCP exposes only 2 tools with minimal definitions. Both tools have descriptions (subscribe: 47 chars, suggest: 45 chars) meeting the 10-1024 char baseline, but lack critical depth. Input schemas are present but extremely sparse: each tool accepts a single string parameter with minimal context. No output schemas are documented. No error handling guidance, no parameter constraints, no recovery paths. Tool names lack action verbs (subscribe/suggest are acceptable but generic). The codebase shows this is a gateway/proxy server, not a primary tool provider, the real tools come from garmin_mcp worker. However, the two exposed tools are underdeveloped for production use.
Subscribe an email address to the MissingMCP newsletter
Submit a feature suggestion or feedback
No output schemas documented for either tool. LLMs cannot infer what fields to expect or plan downstream operations.
Input parameters lack descriptions. 'email' and 'suggestion' parameters have minimal context, no format hints, validation rules, or constraints.
No error handling guidance. Tools do not document what happens on failure (invalid email, duplicate subscription, etc.) or how to recover.
Tool descriptions are generic and lack WHEN/WHY context. 'Subscribe an email address' does not explain when to use this vs other actions or what the user should expect.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
No idempotency or confirmation semantics. Both tools modify state (subscribe adds email, suggest stores feedback) but lack dry-run, confirmation, or idempotent guarantees.