Apollo

Fallback Web Search

fallback_web_search

Search recent news and topics via DuckDuckGo when primary sources fail, with anti-poisoning filters for clean results.

Instructions

Zero-cost DuckDuckGo search fallback for recent news, product launches, and general topics. Applies anti-poisoning filter to all retrieved snippets.

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": "fallback_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.0Sep 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It adds useful facts beyond the schema: 'zero-cost' and the anti-poisoning filter applied to snippets. It does not, however, explain limitations, failure behavior, or what the filtered result set looks like.

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?

Two tight sentences deliver the core purpose, scope, cost trait, and filtering behavior with no filler. The most decision-relevant information is front-loaded.

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?

For a simple two-parameter search tool with an output schema, the description is largely sufficient for an agent to invoke it correctly. The main gap is the underspecified fallback trigger, but the operational context is otherwise clear.

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?

Schema description coverage is 0%, and the description does not explain either parameter. While 'query' and 'max_results' are fairly self-explanatory from names and schema defaults, the description adds no meaning beyond what the input schema already provides.

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

Purpose4/5

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

The description clearly states the tool performs a DuckDuckGo search and specifies topical scope ('recent news, product launches, and general topics'). It is distinguishable from academic/repository-focused siblings by the explicit 'general topics' scope, though it does not name a specific sibling for contrast.

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

Usage Guidelines3/5

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

The word 'fallback' implies this tool is used when primary search options are unavailable or unsuitable, and the topic list gives useful context. However, it never explicitly states when to use this tool versus alternatives or when not to use it, leaving the fallback trigger to inference.

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

Deploy Server