A Spring Boot-based MCP server implementation demonstrating local and remote tool management with MCP client/server architecture
Critical gaps across all dimensions. Tool definitions are inferred from test files only (GetToolsDefinitionsIT.java), not from actual source code registration. No input schemas visible in provided code. Descriptions are present but minimal (34-72 chars, below 194-char baseline). No parameter-level documentation. No output schema documentation. No error handling guidance. Tool names lack clear verb-noun structure (e.g., 'ticketBookingService' vs 'book_tickets'). This is a demonstration/test project, not production-grade.
Get suggestion of good books for a given genre. Also set the limit of books titles to return
Lookup the stock price by company name
Book tickets for a movie. Input parameters are movie name and total count of tickets to book
Get the available ticket count by movie name
Get the weather for the given location or village or town or city. The getWeatherRequest takes location along with unit in Celsius or Fahrenheit.
No input schemas visible in source code. Tool definitions inferred from test assertions only, not from actual tool registration code. Cannot verify parameter types, constraints, or descriptions.
Tool names use camelCase service naming (e.g., 'ticketBookingService') instead of verb_noun pattern (e.g., 'book_tickets'). LLMs cannot infer action intent from service names.
Descriptions lack parameter-level documentation. 'weatherService' mentions 'getWeatherRequest' and 'unit' but provides no guidance on valid unit values, format, or constraints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 34 | 2026-07-28+ | v2 |
No output schema documentation. Callers cannot know what fields to expect from responses, breaking downstream tool chaining and forcing LLMs to guess field names.
No error handling guidance. Descriptions do not indicate what errors are possible, whether they are retryable, or what the LLM should do next.