A MySQL MCP (Model Context Protocol) server implementation for building AI agents
MySQL MCP has 13 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (10-50 chars, mostly under the 50-200 char LLM-optimized range), and input schemas are present with type definitions. However, descriptions lack actionable context (WHEN to use, prerequisites, consequences). Parameter descriptions are minimal (e.g., 'Connection ID' repeated 12 times). No output schemas documented. Error handling is absent, no guidance on retryability, recovery steps, or invalid input handling. Tool naming is verb-first (good), but descriptions don't explain state-modifying consequences or dependencies. Missing: pagination guidance for query results, dry-run/confirmation for destructive ops (delete, drop_table, drop_index), and field-level output documentation.
Create an index
Create a new schema
Create a new table
Delete a row from a table
Describe a table
Drop an index
Drop a table
Execute an INSERT statement
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., what does query() return? Rows? Column names? Metadata?). Every tool lacks return type documentation.
Destructive operations (delete, drop_table, drop_index) lack confirmation/dry-run support and error recovery guidance. No description warns of irreversibility or suggests confirmation patterns.
Parameter descriptions are generic and repeated ('Connection ID' appears 12 times). No guidance on format, constraints, or dependencies. E.g., query() says 'Single SQL query, could return multiple rows. Caller should properly limit the number of rows returned', but no limit parameter exists and no pagination guidance provided.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | <=2025-11-25 | v2 |
List all tables
Execute a SELECT query
Register a new Postgres connection
Unregister a Postgres connection
Execute an UPDATE statement
No error handling or recovery guidance. Tools do not document what errors are retryable, what user-fixable errors look like, or how to recover from SQL syntax errors, connection failures, or permission denials.
Tool descriptions do not explain state-modifying consequences. E.g., insert/update/delete descriptions do not state 'This modifies the database' or 'This operation is not reversible without a backup'. Agents need explicit state-change warnings.