A Model Context Protocol (MCP) server that provides search and crawl functionality using Search1API
Server provides 6 tools with complete input schemas and descriptions. Naming follows verb_noun convention (search, news, crawl, sitemap, reasoning, trending). However, descriptions are minimal (10-50 chars), lacking context on WHEN to use each tool or what distinguishes them. Parameter descriptions are present but generic. No output schemas documented. Error handling not visible in tool definitions. Tools lack idempotent/destructive hints. Composition is reasonable (single responsibility per tool), but chaining support unclear, no evidence that tool outputs contain IDs needed by downstream tools.
Extract content from URL
News search tool
Deep thinking and complex problem solving
Web search tool
Get all related links from a URL
Get trending topics from popular platforms
Tool descriptions are too brief (10-50 chars). LLMs cannot determine WHEN to use each tool or how it differs from similar tools. 'Web search tool' and 'News search tool' lack context on search_service selection, crawl_results behavior, or result structure.
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields. What fields does search() return? Are there pagination cursors? Does crawl() return markdown or HTML?
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). All tools are marked READ_ONLY in metadata, but this is not reflected in tool definitions. Agents cannot determine retry safety or side effects.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | <=2025-11-25 | v2 |
Parameter descriptions lack format/constraint guidance. 'Search query, be simple and concise' does not specify length limits, character restrictions, or examples. 'Number of results to return' lacks min/max bounds (e.g., 1-100).
Error handling not visible in tool definitions. No recovery guidance, error classification, or actionable error messages documented. Handlers exist (src/tools/handlers.js) but error contract is opaque to LLMs.