Spring Boot MCP server providing database tools for querying and managing MySQL tables
Server has 4 read-only database tools with basic descriptions and partial schemas. All tools start with action verbs (getTables, tableExists, getRowsPaginated, searchRows), which is good. However, descriptions are minimal (10-60 chars), parameter descriptions are sparse or missing, and output schemas are not documented. The searchRows tool has a complex 'conditions' parameter (type: object) with no schema definition for the nested structure. Error handling exists but returns generic strings rather than actionable guidance. No tool annotations (readOnlyHint, etc.) despite all being read-only. Overall structure is functional but falls short of production quality.
Retrieve rows from a specified table with pagination
Retrieve available tables in the database
Search for rows in a table using column conditions with various operators
Check if a table exists in the database
Output schemas not documented. LLMs cannot infer what getTables(), getRowsPaginated(), or searchRows() return. No field names, types, or structure specified.
searchRows 'conditions' parameter is type:object with no schema for nested structure. LLMs cannot determine what 'operator' and 'value' fields accept or what operators are valid (e.g., =, >, LIKE, IN).
Descriptions are too short (10-60 chars). getTables is 'Retrieve available tables in the database' (47 chars), lacks context on when to call it or what it returns. Baseline is 194 chars for A+ tools.
Error responses are generic strings ('Error retrieving tables: ...') rather than actionable guidance. No recovery hints or error classification (retryable vs. fatal).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | 2026-07-28+ | v2 |
No tool annotations despite all tools being read-only. Missing readOnlyHint annotation that would signal to agents these are safe to call without side effects.