An MCP server that provides read-only SQL query execution capabilities for Microsoft SQL Server databases
Single tool 'execute_sql' has a clear, descriptive name and good description (127 chars, within 10-1024 range). Input schema is present with type and description. However, output schema is NOT documented, the tool returns a map[string]interface{} with 'columns'/'rows' or 'rowCount' fields, but this structure is never formally declared in the tool definition. No parameter constraints (enums, ranges, patterns) despite accepting arbitrary SQL. Error handling returns generic error strings without recovery guidance. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite the tool being explicitly read-only. The write-operation check via regex is a runtime guard, not a schema-level constraint.
Execute a read-only SQL query on the MSSQL server. Write operations (CREATE, ALTER, DROP, INSERT, UPDATE, DELETE, etc.) are not permitted.
Output schema not documented. Tool returns map with 'columns'/'rows' or 'rowCount' fields, but LLM has no formal schema to plan downstream operations or extract results reliably.
No tool annotations despite explicit read-only constraint. Missing readOnlyHint annotation prevents clients from optimizing caching, retry logic, or permission checks.
Query parameter accepts free-form string with no constraints. Should declare format (SQL), length limits, or forbidden patterns (e.g., regex for write operations) in schema, not just runtime checks.
Error messages lack recovery guidance. 'Write operations are not permitted' tells LLM nothing about what to do next. Should suggest 'Use read-only queries (SELECT, DESCRIBE, SHOW)' or offer alternative tools.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | <=2025-11-25 | v2 |
No pagination support. Tool accepts arbitrary queries but does not document result limits or offer offset/limit parameters. Large result sets could exhaust context window.