MCP Web Fetch Server

web_search

Read-only

Retrieve titles, URLs, and snippets from top web search results via DuckDuckGo, with automatic fallback to a local SearXNG if needed.

Instructions

Search the web via DuckDuckGo (no API key required) and return titles, URLs, and snippets for the top matches. Automatically falls back to a local SearXNG instance (FETCH_SEARXNG_URL) if DuckDuckGo's scrape fails.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "web_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes
`max_results`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description reveals that the tool uses DuckDuckGo (no API key required) with an automatic fallback to a local SearXNG instance, which adds behavioral context beyond the readOnlyHint annotation. It does not mention rate limits or result freshness, but the core behavior is well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, front-loading the primary function in the first sentence and adding a crucial fallback detail in the second. Every word serves a purpose, making it highly efficient and easy to process.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core action, output components (titles, URLs, snippets), and fallback behavior. However, it omits mention of result count limit, caching, or error handling. Given the presence of an output schema, the description is fairly complete but could optionally address these points.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, meaning the description adds no meaning to parameters beyond the schema. It does not explain what 'query' or 'max_results' entail, nor their expected format. The description mentions 'top matches' but does not link it to the max_results parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'Search the web' via DuckDuckGo and returns titles, URLs, and snippets. It uniquely identifies the resource (web) and action (search), distinguishing it from sibling tools like fetch_url or batch_fetch that handle individual URLs or file operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for general web search queries and mentions a fallback mechanism, but does not explicitly specify when not to use it or provide direct comparisons to siblings. The context from sibling names helps, but the guideline is not fully explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server