A simple MCP server providing calculator tools without authentication, deployed on Cloudflare Workers
Two tools with basic schemas and minimal descriptions. Both tools have input schemas with proper types (number, enum), but descriptions are extremely short (10-40 chars), falling well below the 50-200 char baseline for LLM-optimized descriptions. No output schema documentation. Error handling is minimal (divide-by-zero check in calculate, but no recovery guidance). Tool names lack action verbs ('add' and 'calculate' are weak; 'perform_addition' and 'perform_calculation' would be clearer). No parameter descriptions beyond type hints. Schemas are present but sparse.
Simple addition tool
Calculator tool with multiple operations
Tool descriptions are critically short (10-40 chars). 'Simple addition tool' and 'Calculator tool with multiple operations' lack context for LLM selection. Should explain WHAT the tool does, WHEN to use it, and what it returns (e.g., 'Adds two numbers and returns their sum as a numeric result. Use when you need basic arithmetic addition.').
Parameter descriptions are missing entirely. Zod schema defines types (number, enum) but LLMs cannot infer meaning from names alone. 'a' and 'b' are ambiguous, are they operands, indices, or coefficients? Add descriptions like 'First operand (numeric value)' and 'Second operand (numeric value)'.
No output schema documented. LLMs cannot plan downstream calls or extract results reliably. Document that both tools return a text response containing the numeric result. Specify format: 'Returns a text response with the computed result as a string (e.g., "15" for 10+5).'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |
Tool names lack action verbs. 'add' and 'calculate' are weak; they don't clearly distinguish intent. Rename to 'perform_addition' or 'add_numbers' (verb_noun pattern) and 'perform_arithmetic' or 'calculate_expression' to improve LLM disambiguation.
Error handling is minimal. The divide-by-zero check returns a text error message, but does not guide the LLM on recovery. Should return a structured error with actionable guidance: 'Cannot divide by zero. Ensure the second operand (b) is non-zero and retry.'