MCP server for searching and interacting with GitHub repositories
Single tool with minimal definition quality. Tool name 'general_search' is generic and lacks action clarity (should be 'search_repositories'). Description is adequate (56 chars) but lacks context on when to use vs alternatives, prerequisites, or return structure. Input schema present but parameter description is minimal (27 chars, below 72-char baseline). No output schema documented, LLM cannot predict response structure. No error handling guidance. No pagination support despite search results potentially being large. Tool follows basic FastMCP registration but lacks production-grade polish.
Search GitHub repositories with the given keyword.
Generic tool name 'general_search' lacks action clarity. Should be 'search_repositories' to match GitHub API semantics and help LLM infer intent.
No output schema documented. LLM cannot predict response structure (total_count, items array with name/url/description fields). Must document return type explicitly.
No pagination support. Search results unbounded, could return hundreds of repos, exhausting context window. Must add limit and offset/cursor parameters.
Parameter description 'Search term to look for on GitHub' is minimal (27 chars, below 72-char baseline). Should explain format constraints, example queries, and when to use.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
No error handling guidance. Tool will fail silently on invalid tokens, rate limits, or malformed queries. Must return actionable error messages with recovery steps.