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 (number, number) and minimal descriptions. Tool name lacks action verb (should be 'add_numbers'). Description is extremely terse (5 words, well below 20-char threshold). No output schema documented. No error handling guidance. Parameter descriptions are present but generic. This is a toy/demo server with minimal production-grade tooling.
Adds two numbers together
Tool name 'add' lacks action verb. Should be 'add_numbers' or similar to match verb_noun convention. LLMs rely on names to infer intent before reading descriptions.
Tool description 'Adds two numbers together' is only 28 characters, below the 50-char minimum for LLM clarity. Should explain WHEN to use it, what it returns, and any constraints (e.g., 'Computes the sum of two numbers. Returns the result as a text string. Useful for arithmetic operations in multi-step calculations.').
Output schema is not documented. Tool returns {content: [{type: 'text', text: string}]} but this structure is not declared in the tool definition. LLMs cannot plan downstream calls or extract results reliably without knowing the response shape.
No error handling or recovery guidance. What happens if inputs are NaN, Infinity, or non-numeric? Tool should document constraints (e.g., 'Accepts integers and floats. Returns error if inputs exceed ±1e308.') and guide recovery.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
Parameter descriptions are minimal ('First number to add', 'Second number to add'). Should specify format, range, and constraints: 'First operand (number, range ±1e308, supports integers and floats).'