A Cloudflare Workers-based MCP server with OAuth 2.0 authentication and a simple arithmetic tool
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. No parameter descriptions beyond type hints. The tool is trivial (arithmetic) and lacks the depth expected even for demo servers. Baseline: A+ tools average 194 chars in description; this is 11.
Adds two numbers together
Tool description is critically short (11 chars). Must be 20 - 1024 chars and explain WHAT, WHEN, and any prerequisites. Current: 'Adds two numbers together' lacks context on use case, return format, or error conditions.
No output schema documented. LLMs cannot plan downstream calls or extract results without knowing the response structure. Must document return type (e.g., 'Returns {result: number}').
Input parameters lack descriptions. 'a' and 'b' have types (number) but no descriptions explaining what they represent, valid ranges, or constraints. LLMs cannot infer meaning from names alone.
No error handling guidance. What happens if inputs are NaN, Infinity, or non-numeric? How should the LLM recover? No recovery guide provided.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
Tool is trivial (basic arithmetic). For a production MCP server, this demonstrates no real-world utility. Consider replacing with domain-specific tools (e.g., calculate_invoice_total, compute_project_budget) to validate the framework.