A simple calculator MCP server with basic arithmetic operations
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) and lack context for LLM selection. No output schema documentation. Error handling present in 'calculate' (divide-by-zero) but not generalized. Tool names are clear action verbs ('add', 'calculate') but descriptions fail to explain WHEN to use each tool or distinguish between them. No parameter descriptions beyond type hints in schema.
Simple addition tool
Calculator tool with multiple operations
Tool descriptions critically short (10-40 chars). 'Simple addition tool' and 'Calculator tool with multiple operations' lack context for LLM selection. Baseline is 194 chars; these are 90% below baseline.
No parameter descriptions in schema. Zod schema defines types but LLMs cannot read JSON Schema directly, they need human-readable descriptions. Parameters 'a', 'b', 'operation' lack explanatory text.
No output schema documented. Tool responses return text content but LLMs have no formal specification of return structure. Baseline: 100% of A+ tools document return types.
Duplicate functionality. Both 'add' and 'calculate' perform addition. 'add' is redundant when 'calculate' with operation='add' exists. This forces LLM to reason between two tools doing the same thing.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Error handling only in 'calculate' (divide-by-zero). No guidance for LLM on recovery. Error message 'Cannot divide by zero' is user-facing but lacks actionable next steps per pattern:recovery-guide.