MCP server for restaurant menu and receipt management with PostgreSQL backend
Single tool 'calculate' has a clear verb-noun name and proper schema with typed parameters (string, number). Description is adequate (47 chars) but minimal. All three parameters have descriptions and the operation param correctly uses an enum constraint. However, the tool description lacks context about when to use it vs alternatives, and the output format is undocumented (returns formatted string, not structured object). Error handling for division by zero is present but generic. No tool annotations (readOnlyHint, etc.) despite being READ_ONLY. Overall functional but lacks production polish.
Perform basic arithmetic operations
Tool description lacks context and selection guidance. 'Perform basic arithmetic operations' does not explain when to use this tool, what it returns, or any prerequisites. LLMs need explicit guidance to select tools correctly.
Output schema is undocumented. Tool returns a formatted string (e.g. '3.14') but LLMs cannot infer the structure. Responses should be documented as structured objects with typed fields for reliable downstream processing.
Tool is marked READ_ONLY but has no tool annotations (readOnlyHint). Explicit annotations enable agents to reason about safety and retry behavior without guessing.
Error message for division by zero is generic ('cannot divide by zero'). Should include guidance: 'Cannot divide by zero. Ensure y is non-zero and retry.'
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | <=2025-11-25 | v2 |
Server exposes only one trivial tool (calculator). No domain-specific tools for the stated purpose (restaurant menu/receipt management). The codebase includes menu, receipt, and postgres packages but no corresponding MCP tools.