MCP server providing mathematical calculations, unit conversions, date formatting, and natural language to SQL query generation with HR database schema support
Server has 4 tools with basic schemas and descriptions, but significant quality gaps. Tool naming lacks action verbs (e.g., 'nl-to-sql' should be 'convert_nl_to_sql'). Descriptions are present but generic, 'calculate' description is just the parameter description, not a tool description. Parameter descriptions exist but lack constraints (e.g., 'expression' has no format guidance, 'convert' lacks unit enum). Error handling is minimal (generic 'Could not evaluate' messages). No output schemas documented. The 'nl-to-sql' tool is particularly concerning: it accepts arbitrary natural language queries against an HR database with no input validation, rate limiting, or permission checks. Tool composition is reasonable but descriptions don't explain when to use each tool vs. alternatives.
The mathematical expression to evaluate
Convert values between different units (temperature, distance, weight)
Format a date string according to a specified format pattern
Convert natural language to SQL for our HR database. Available tables: employees (with personal details, salary, department_id, manager_id), departments (id, name, location, budget), projects (id, name, dates, status, budget), employee_projects (assignments of employees to projects). Examples: 'Find employees in IT earning over 70k', 'List projects ending this year', 'Show managers with most direct reports'
Tool 'calculate' uses eval() without sanitization. Description is parameter-level, not tool-level. No output schema documented.
Tool 'nl-to-sql' accepts arbitrary natural language queries against HR database with no input validation, rate limiting, or permission checks. No enum constraints on query types. Exposes database schema details in description.
Tool 'convert' lacks enum constraints for fromUnit/toUnit parameters. Description does not list valid units or format constraints.
Tool naming does not follow verb_noun convention. 'nl-to-sql' should be 'convert_nl_to_sql', 'format-date' should be 'format_date'. Hyphens instead of underscores reduce LLM parsing clarity.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | <=2025-11-25 | v2 |
No error recovery guidance. Error messages are generic ('Could not evaluate expression'). LLM cannot determine if error is retryable or user-fixable.