MCP server with OAuth 2.0 authorization provider running on Cloudflare Workers, demonstrating remote authentication flows
Single tool 'add' has a clear verb-noun name and basic schema with typed parameters. However, the description is minimal (22 chars) and lacks context about when/why to use it. Parameters 'a' and 'b' have descriptions but are generic. No output schema is documented. No error handling guidance. The tool is trivial (arithmetic) and does not reflect production patterns. Baseline: 194 chars for tool descriptions, 72 chars for param annotations, this server falls well short.
Adds two numbers together
Tool description is too short (22 chars) and lacks context. Should explain what the tool does, when to use it, and what it returns. Current: 'Adds two numbers together', no guidance on use case or output format.
Output schema is not documented. LLMs cannot infer what fields the response contains or how to chain this tool with others. Must document return type (e.g., 'Returns {result: number}').
No error handling or validation guidance. What happens if inputs are null, NaN, or Infinity? Tool should document constraints (e.g., 'Accepts integers and floats; returns number or error if overflow') and recovery steps.
Parameter descriptions are minimal. 'First number to add' and 'Second number to add' lack format/range constraints. Should specify: 'A numeric value (integer or float, range -1e308 to 1e308)' to guide LLM input.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | 2026-07-28+ | v2 |
Tool is trivial (basic arithmetic) and does not demonstrate production patterns. A real MCP server should include tools for meaningful operations: data retrieval, state mutation, integration with external services. This toy example does not validate server quality.