MCP WebSearch server — DuckDuckGo Lite search tool for the Model Context Protocol
Single tool 'web_search' has a well-crafted description (186 chars) that explains WHAT, WHEN, and WHY to use it, matching production baselines (avg 194 chars). Input schema is present with proper JSON Schema structure and a typed 'query' parameter. However, the parameter description is minimal ('The search query'), and the output schema is not documented in the visible code. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present. Error handling and recovery guidance are not visible. The tool name 'web_search' correctly starts with a verb and is unambiguous. Overall, this is a solid single-tool implementation with room for parameter detail and output documentation.
Search the web for current information. Returns titles, URLs, and snippets. Before answering questions about recent events, news, current prices, weather, or anything time-sensitive, search first. Also use this when you're unsure about facts or the user asks you to look something up.
Parameter description is minimal. 'The search query' (18 chars) lacks guidance on format, length, or constraints. Should explain expected input (e.g., 'Natural language search terms, 1-500 characters. Supports boolean operators and site: filters.').
Output schema is not documented in visible code. LLMs cannot plan downstream operations without knowing what fields are returned (titles, URLs, snippets, result count, etc.). Add explicit output schema documentation.
No tool annotations present. The tool is read-only (risk: READ_ONLY), but readOnlyHint is not declared in the schema. This prevents clients from optimizing caching and retry logic.
Error handling and recovery guidance not visible. If DuckDuckGo is unreachable or returns no results, what should the LLM do? Add error classification (retryable, user-fixable, fatal) and recovery hints.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 68 | <=2025-11-25 | v2 |
No pagination or result limit documented. If DuckDuckGo returns 100+ results, how many does the tool return? Add limit parameter and document max_results behavior (currently hardcoded to 5 in config, but not exposed in tool schema).