MCP server with OAuth 2.0 authorization provider running on Cloudflare Workers, demonstrating remote MCP authentication and authorization flows
Single tool 'add' has a clear verb-noun name and basic schema with typed parameters (number, number). However, the description is extremely minimal (11 chars: 'Adds two numbers together'), falling below the 20-char threshold and providing no context on when/why to use it. No output schema is documented. No error handling guidance. The tool is trivial and does not reflect production patterns for parameter descriptions, output structure documentation, or error recovery.
Adds two numbers together
Tool description is too short (11 chars) and lacks context. Must be 20 - 1024 chars and explain WHAT, WHEN, and any prerequisites.
Output schema is not documented. LLMs cannot plan downstream calls or extract results without knowing the response structure.
Parameter descriptions are minimal. 'First number to add' and 'Second number to add' lack format, range, or constraint details.
No error handling or recovery guidance. What happens if inputs are NaN, Infinity, or null? How should the LLM respond?
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |