An MCP server that provides web search capabilities using DeepSeek's Anthropic-compatible API.
Two tools with complete schemas and descriptions. web_search has well-structured input parameters (query, max_uses, allowed_domains, blocked_domains, user_location) with proper type constraints and descriptions. web_search_stats has simpler but valid schema. Both descriptions exceed 100 chars and explain purpose clearly. However, output schemas are not formally documented, responses are JSON strings without declared field structure. Parameter descriptions are adequate but lack actionable guidance on error recovery or prerequisites. No tool annotations (readOnlyHint, idempotentHint) present. Error handling returns JSON payloads but lacks recovery guidance per pattern:recovery-guide.
Search the web using DeepSeek's built-in web search. Returns a JSON payload containing the model's synthesized answer, the list of source results (title/url/pageAge/searchQuery), the search queries actually issued, token usage and other metadata. Each search call returns ~10 results. Use max_uses to request additional keyword variations.
Query hourly search statistics as a JSON payload. Returns per-hour search counts within a time range. If no time range is specified, defaults to today (from 00:00 to now).
Output schemas not formally documented. Both tools return JSON text responses without declared field structure. LLMs cannot plan downstream operations or extract fields reliably.
Error responses lack recovery guidance. Errors return JSON with 'error' field but do not suggest next steps (e.g., 'Try with a shorter query' or 'Check API key configuration').
No tool annotations. Neither tool declares readOnlyHint, destructiveHint, or idempotentHint. Both are read-only but lack explicit annotation.
Parameter descriptions lack actionable constraints. 'Search query' and 'Max number of search calls' are generic. Should specify: 'Natural language query (1-500 chars); avoid special operators' and 'Each call returns ~10 results; higher values increase latency and cost'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
web_search_stats parameter descriptions lack clarity on default behavior. 'Defaults to today at 00:00:00' and 'Defaults to now' are stated but not in the description text itself, only in the tool description. Parameter descriptions should be self-contained.