A Spring Boot-based MCP server for MySQL database operations
Single tool 'queryMysql' with critical definition gaps. Description is minimal (12 chars: 'mysql查询'), below the 20-char hard floor. Input schema present but parameter description is generic ('标准查询sql' = 'standard query sql'). No output schema documented. No error handling guidance. Tool lacks context on when to use it, what it returns, or how to handle failures. Naming is acceptable (verb_noun pattern) but insufficient to compensate for missing descriptions and schemas.
mysql查询
Tool description is 12 characters ('mysql查询'), below 20-char minimum.
No output schema documented. LLM cannot predict return type, structure, or fields. Breaks downstream tool chaining and forces guessing.
Parameter description 'sql' → '标准查询sql' is generic. No guidance on format, constraints, or examples. Missing: expected SQL dialect, max query length, allowed operations (SELECT only?), or error cases.
No error handling or recovery guidance. If query fails (syntax error, timeout, permission denied), LLM has no actionable next step.
SQL injection risk: tool accepts raw SQL string with no sanitization visible in McpServiceTools.java. LLM could be tricked into passing malicious queries.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 35 | 2026-07-28+ | v2 |