MCP server that provides cocktail recipe search functionality via TheCocktailDB API
Single tool with basic schema and minimal description. Tool name 'get_cocktail' follows verb_noun convention (+), but description is only 34 chars, below the 50-char baseline for clarity. Input schema is present with proper JSON Schema structure, but lacks parameter constraints (no enum, pattern, or range). No output schema documented. Error handling returns isError flag but lacks recovery guidance or actionable next steps. No tool annotations (readOnlyHint, etc.). Overall: functional but sparse, typical of early-stage community servers.
Search for cocktail recipes by name
Tool description too brief (34 chars). Lacks context on when to use, what it returns, or prerequisites. LLMs cannot reliably select this tool without more detail.
No output schema documented. LLMs cannot plan downstream operations or extract structured data from results. Responses are free-text formatted strings, not typed objects.
Error messages lack recovery guidance. 'Error searching for cocktail: <message>' tells LLM nothing about what to do next. Should suggest retry, alternative search terms, or fallback actions.
No input validation constraints. Parameter 'name' accepts any string; no length limits, pattern, or guidance on format. LLMs may pass empty strings or extremely long queries.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
No tool annotations. Missing readOnlyHint (this is a read-only query), which prevents agents from understanding idempotency and safety properties.