MCP server with OAuth 2.0 authorization provider running on Cloudflare Workers, demonstrating remote MCP authentication and authorization 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'). Parameter descriptions are present but generic (10-20 chars each). No output schema documented. No error handling guidance. No tool annotations. Composition is trivial (pure math). This is a demo/toy server, not production-grade.
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.
No output schema documented. LLMs cannot plan downstream calls or extract results without knowing the response structure. Current implementation returns text content but this is not formally specified.
Parameter descriptions are too brief (10-20 chars). 'First number to add' and 'Second number to add' lack context on format, range, or constraints. Baseline for A+ tools is 72 chars average.
No error handling or recovery guidance. What happens if non-numeric input is passed? How should the LLM respond to failures?
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). This tool is read-only and idempotent but these properties are not declared in the schema.