Find MCP servers from the awesome-mcp-servers list
Single tool 'find-mcp-servers' has a clear action verb and reasonable description (89 chars), but lacks critical depth. Input schema is present with proper Zod types and descriptions, but output schema is undocumented, LLMs cannot predict the response structure. No error handling guidance, no pagination despite fetching external data that could return large result sets. Parameter descriptions are adequate but lack format/constraint details. Tool performs a single, well-defined action (search MCP servers), but implementation quality is below production baseline.
Find MCP servers from the awesome-mcp-servers list
Output schema is undocumented. Tool returns formatted text strings, but LLMs cannot parse or chain results. No structured response definition provided.
No pagination or result limiting guidance in tool description. External data fetch could return hundreds of servers; tool caps at limit=100 but description does not explain this constraint or when pagination is needed.
No error handling or recovery guidance. If external README fetch fails, tool returns empty array silently. LLM receives no indication of failure vs. no results, cannot retry or ask user.
Parameter descriptions lack format/constraint details. 'search' and 'tag' accept free-form strings with no guidance on case sensitivity, partial matching, or emoji handling. Invites LLM confusion.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |
Tool description does not explain when to use it or what it returns. 'Find MCP servers from the awesome-mcp-servers list' is minimal, missing context on use cases, response format, and limitations.