An MCP server that provides item search functionality over HTTP
Single tool 'search_items' is well-defined with clear naming, comprehensive description (89 chars), and complete input/output schemas using Zod. Tool name starts with action verb 'search' and accurately reflects behavior. Input schema includes proper type constraints (minLength, min/max for limit). Output schema is documented with structured results array. Tool annotations (readOnlyHint) are present. No destructive operations, so confirmation patterns not applicable.
Search item titles by keyword and return matching IDs.
Missing parameter descriptions in schema. The 'limit' parameter has no description field in the Zod schema, only a default and constraints.
No error handling or recovery guidance. Tool lacks documentation of failure modes (e.g., what if query is empty after validation, or no results found). Error responses should guide the LLM on next steps.
Output schema lacks pagination support. Results array is unbounded; no limit enforcement or next_cursor documented.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | B | 71 | 2025-06-18+ | v2 |