Calculator MCP Server with dice rolling and arithmetic operations
This is a basic calculator MCP server with 6 simple tools. All tools are explicitly registered via @mcp.tool decorators in main.py. Naming follows verb_noun convention (add_numbers, divide_numbers, etc.) which is good. However, descriptions are extremely brief (10-30 chars), well below the 10-1024 char target and 194 char baseline. Parameter descriptions are minimal or missing context. Input schemas are present with basic types but lack validation details, constraints, and error guidance. No error handling beyond a single divide-by-zero check. No output schemas documented. The server demonstrates correct FastMCP framework usage but lacks production-grade tool engineering. Tool definitions are directly visible (not inferred), so no hard cap applies. STDIO transport is the critical blocker: this server cannot be used with hosted MCP clients and caps the protocol readiness score at 50.
Add two numbers and return the result.
Divide two numbers and return the result.
Return the modulus of two integers.
Multiply two numbers and return the result.
Roll a specified number of six-sided dice and return the results.
Subtract two numbers and return the result.
Tool descriptions are critically short (10-30 characters). Rubric baseline is 194 chars. 'Add two numbers and return the result.' lacks context for when LLM should call this vs. alternatives, prerequisites, or return type details. Descriptions under 20 chars incur hard penalty.
Parameter descriptions are minimal or missing guidance. E.g., 'n_dice' parameter in roll_dice has description 'Number of six-sided dice to roll' but does not specify valid range (1-100? 1-1000?). LLMs will guess and may pass absurd values. Rubric requires min/max for numeric params and format guidance.
No output schemas documented. While tools return simple types (float, int, list[int]), LLMs cannot plan downstream tool calls or extract data without knowing the response structure. For list returns like roll_dice, lack of pagination, total count, or next_cursor is a gap.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 46 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 46 | - | v1 |
Error handling is minimal. Only divide_numbers includes a check (division by zero). modulus_numbers does not guard against modulus-by-zero. No error response guides LLM recovery (e.g., 'Cannot divide by zero, check second parameter is not 0'). Rubric requires error categorization and actionable recovery steps.
STDIO transport only. Server cannot be remotely accessed or integrated with hosted MCP clients. This is a hard blocker for production use. Rubric caps protocol readiness at 50 for STDIO-only servers.