A simple MCP server providing calculator tools without authentication
Two tools with minimal descriptions and basic schemas. 'add' (9 chars) and 'calculate' (10 chars) descriptions are far below the 50-200 char baseline for LLM-optimized tools. Both tools lack parameter descriptions entirely, critical gap per pattern:tool-description. Schemas are present but sparse. No error handling guidance, no output schema documentation, no composition hints. Tools are simple arithmetic operations with no real-world complexity, but even simple tools need proper documentation for agent selection and error recovery.
Simple addition tool
Calculator tool with multiple operations
Tool descriptions critically short (9-10 chars). Baseline is 50-200 chars. LLMs cannot determine when/why to select these tools.
No parameter descriptions. 'a', 'b', 'operation' lack context. LLMs cannot infer whether 'a' is an account ID, amount, or operand without explicit description.
No output schema documented. Callers do not know what fields to expect or how to chain results to downstream tools.
No error handling guidance. 'divide' returns plain text error for zero division, but no structured error classification or recovery hints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |
Tool names lack action verbs. 'add' and 'calculate' are generic. 'perform_addition' and 'perform_arithmetic' would be clearer; 'calculate' alone does not distinguish from other math tools.