A simple MCP server providing calculator tools without authentication
Two tools with basic schemas and minimal descriptions. Both tools have input schemas with proper types (number, string 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' returns plain text, not structured error 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 WHEN to use each tool, what they return, and any prerequisites.
No parameter descriptions. Zod schema defines types but LLMs cannot read JSON Schema directly. Each parameter (a, b, operation) needs a text description explaining its role, valid range, and format.
Output schema not documented. Tool responses return plain text in a content array, but LLMs have no schema to understand the structure. Document: 'Returns {content: [{type: "text", text: string}]}'.
Error handling lacks recovery guidance. 'calculate' returns 'Error: Cannot divide by zero' as plain text. Should return structured error: {error: 'DIVISION_BY_ZERO', message: 'Cannot divide by zero. Ensure b is non-zero.', retryable: false}.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
Tool names lack action verbs. 'add' and 'calculate' are generic. Better names: 'perform_addition', 'perform_arithmetic' or 'compute_sum', 'compute_result'. Verb-noun naming helps LLMs parse intent.