A lightweight Spring Boot starter for building Model Context Protocol (MCP) servers in Java
This Spring Boot MCP starter demonstrates basic tool annotation infrastructure but suffers from critical gaps in schema completeness, parameter documentation, and error handling. Tools are defined with minimal descriptions and lack output schema documentation. The 4 test tools (greet, add, search, echo) have incomplete input schemas visible only in test files, not in a production tool registration system. Naming is reasonable (verb-first: greet, add, search, echo), but parameter descriptions are minimal (often single words like 'User's name', 'First number'). No error handling guidance, no pagination for list operations, no output schema documentation. The infrastructure shows promise but the actual tools fail to meet production-grade agentic tool standards.
Adds two numbers
Echoes input back
Greets a user by name
Search with optional limit
Output schemas completely undocumented. No tool describes what fields it returns, type structure, or what the LLM should expect. This forces agents to guess output format and breaks downstream tool chaining.
Parameter descriptions are too minimal (1-3 words). 'User's name', 'First number', 'Search query', 'Message to echo' provide no context on format, constraints, or use patterns. LLMs need 10-50 char descriptions minimum to understand intent.
No error handling guidance. Tools provide no recovery hints (e.g., 'If search returns no results, try a broader query'). Agents cannot self-correct or understand failure modes.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 45 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 27 | 2025-03-26+ | v1 |
Search tool accepts 'limit' parameter but no documentation on default, max value, or pagination support. Returns 'Max results' but no explanation of how pagination works or what cursor field is returned.
Tool definitions exist only in test files (ToolResolverTest.java, McpServerTest.java), not in production tool registration. Cannot verify that schemas are actually enforced at runtime or that tool registry properly publishes these definitions to clients.
Parameter type mappings incomplete. 'add' tool shows integer parameters, but 'greet' and 'echo' show string types without clarifying constraints (min/max length, character restrictions). No enum constraints anywhere.
Tool names are generic and lack specificity. 'echo' and 'greet' are vague, what distinguishes echo from a generic passthrough? Does 'greet' send an email, post to chat, or return a string? Ambiguous names invite wrong tool selection.