MCP server with OAuth 2.0 authorization provider running on Cloudflare Workers, demonstrating remote authentication flows
Single tool 'add' has a basic schema with typed parameters (a, b as numbers) and descriptions, but lacks depth expected for production. Tool description is minimal (11 words, 33 chars), below the 10 - 1024 char guideline sweet spot (194 char baseline). No output schema documented. No error handling guidance. No indication of idempotency, side effects, or when to use this tool vs alternatives. The tool is trivial (arithmetic), but even simple tools need complete, LLM-optimized descriptions. Parameter descriptions are present but terse ('First number to add' is adequate but could explain constraints, valid ranges, or format expectations).
Adds two numbers together
Tool description is too short (33 chars vs 194 char baseline). Lacks context on when to use, what it returns, and any prerequisites.
Output schema not documented. LLMs cannot infer what fields the response contains or plan downstream tool calls.
No error handling guidance. If inputs are invalid (non-numeric, NaN, Infinity), the tool provides no recovery path for the LLM.
Tool name 'add' lacks verb_noun clarity. While 'add' is a verb, 'add_numbers' would be more explicit and self-documenting.
No parameter constraints documented (e.g., min/max values, handling of edge cases like very large numbers or negative values).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |