Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. All tools have names starting with action verbs (list_, describe_, run_) and non-empty descriptions (10-100 chars). However, parameter descriptions are minimal or absent, output schemas are undocumented, and error handling is rudimentary. The run_query tool lacks input validation constraints (e.g., no mention of SELECT-only enforcement or row limit enforcement). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all being read-only operations.
Retrieve the column structure, keys, and indexes of a specific table
List all tables and views available in the current database schema
Execute a read-only SQL SELECT query against the database (results capped to 100 rows)
Output schemas undocumented. All three tools return JSON-stringified text without declaring the structure of returned objects (e.g., what fields does TableInfo contain? What columns does ColumnInfo expose?). LLMs cannot plan downstream operations without knowing response structure.
run_query lacks input validation constraints. Description says 'read-only SELECT query' and 'results capped to 100 rows', but the parameter schema has no enum, pattern, or format constraint. No mention of how the 100-row limit is enforced or what happens if exceeded. LLMs cannot verify compliance before calling.
describe_table parameter 'tableName' lacks format guidance. No mention of case sensitivity, schema qualification (public.users vs users), or whether views are included. Ambiguity invites invalid calls.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | <=2025-11-25 | v2 |
No tool annotations despite all being read-only. MCP spec supports readOnlyHint to signal safe operations. Absence forces clients to infer safety from descriptions alone.
Error handling in run_query is minimal. Catch-all returns isError=true with err.message, which may expose SQL syntax errors or database internals to the LLM. No guidance on recovery (e.g., 'Invalid SQL syntax. Check column names and table references.').