CalculatorMCP provides 10 simple arithmetic tools with consistent naming (verb_noun pattern: add, subtract, multiply, etc.) and clear, concise descriptions (10-60 chars). All tools have proper JSON Schema input definitions with typed parameters and descriptions. However, output schemas are not documented, callers cannot see that tools return a double/number. Parameter descriptions are minimal but adequate for simple numeric operations. No error recovery guidance, no tool annotations (readOnlyHint), and no pagination/batching patterns (though not applicable for calculator functions). The server is well-structured for its domain but lacks production-grade error handling and output documentation.

• Document output schema for all tools: declare that each returns a number (double) with optional precision/range notes. E.g., 'Returns: number (IEEE 754 double precision)'.
• Add tool annotations to schema: set readOnlyHint=true and idempotentHint=true for all tools to signal safety properties to LLMs and clients.
• Enhance error messages for divide() and percentage(): return structured errors with recovery hints. E.g., 'Division by zero is not allowed. Ensure divisor (B) is non-zero.' instead of generic ArgumentException.
• Add numeric constraints to parameter descriptions: e.g., 'Dividend (any real number)' or 'Exponent (integer or float, typically -100 to 100)' to guide LLM input generation.
• Verify and document transport mechanism: confirm whether server uses HTTP (Streamable or SSE) or STDIO, and update README with deployment/connection instructions.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry