MCP server providing multi-source search capabilities via Google, Brave, and DuckDuckGo APIs
All three tools have minimal descriptions (20-30 chars) and single-parameter schemas with no type constraints. Naming is verb-based but generic ('search' rather than 'search_web' or 'search_news'). No output schema documentation, error handling guidance, or parameter validation hints. Tools lack descriptions of return format, when to use each variant, or error recovery paths. No pagination, rate-limit guidance, or result limits documented.
Fetch search results from Brave News API.
Query DuckDuckGo Instant Answer API (no key required).
Run a Google search via SerpApi (Custom Search no longer needed).
Descriptions are 20-30 characters, below the 34-char p10 baseline. No guidance on when to use each search engine, what results look like, or error recovery.
No output schema documented. Tools return raw JSON strings; LLMs cannot infer field structure, pagination, or how to extract relevant data.
Query parameter lacks constraints (length, format, language). No guidance on query syntax, special operators, or result limits.
No error handling guidance. RuntimeError for missing GOOGLE_API_KEY is not actionable for LLM. No recovery hints (e.g., 'Set GOOGLE_API_KEY env var').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
Tool names are generic ('google_search', 'brave_search', 'duck_search'). LLMs cannot distinguish use cases. Consider 'search_web_google', 'search_news_brave', 'search_instant_duckduckgo'.