Spring Boot MCP server with chat client integration that exposes tools via MCP protocol and connects to LLM services
Single tool with minimal definition quality. Tool name 'getAuthorByArticleTitle' violates verb_noun convention (should be 'get_author_by_article_title'). Description is 34 chars, below the 50-char minimum for LLM clarity. Input schema present but parameter description is generic ('The title of the article'). No output schema documented. No error handling guidance. No parameter constraints (e.g., min/max length). Tool appears functional but lacks production-grade documentation and structure.
get author detail by article title
Tool name violates verb_noun convention. 'getAuthorByArticleTitle' uses camelCase and lacks underscore separation. Should be 'get_author_by_article_title' for LLM parsing consistency.
Tool description is only 34 characters ('get author detail by article title'). Below 50-char minimum for LLM context. Lacks WHAT, WHEN, and WHY guidance. Should explain: What does 'author detail' include? When should this be called vs. other lookups?
No output schema documented. LLMs cannot plan downstream calls or extract fields without knowing what 'author detail' returns. Must document: fields, types, and required vs. optional properties.
Parameter 'articleTitle' lacks constraints. No min/max length, no format guidance, no examples of valid input. LLMs may pass empty strings, null, or extremely long values.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | 2026-07-28+ | v2 |
No error handling guidance. What happens if article not found? If multiple authors? If database fails? LLM has no recovery path.