multi-api-web-search

Web Search (Alias)

web_search

Search the live internet through multiple AI models, using a single model or hybrid consensus to cross-verify findings and get cited sources.

Instructions

Multi-API Web Search: Live internet search across your configured API models. Supports single model or multi-engine consensus ('hybrid').

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
`model`	No	Optional search engine mode or model name (e.g. 'gemini', 'grok', 'fast', 'hybrid' for multi-engine consensus).
`query`	Yes	Search query or research question in natural language.
`max_sources`	No	Max number of sources to include (1-30, default 15).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.0Sep 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states that the search is live and may span multiple configured API models, but it does not describe result format, failure behavior, rate limits, or what hybrid consensus actually returns. This is minimal behavioral transparency.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no filler. It communicates the core capability efficiently, though it omits deeper usage guidance that would have made it more complete.

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

Completeness3/5

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

For a simple three-parameter search tool, the minimum invocation is well covered by the schema and the live-search statement. However, with no output schema and no annotations, the absence of result-format details and the lack of distinction from the sibling tool leave notable gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all three parameters adequately. The description adds the idea of hybrid consensus but does not meaningfully extend parameter semantics beyond the schema. Baseline 3 is appropriate.

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 identifies a live web search action and explains single-model vs hybrid consensus modes. It names the resource and action, making the tool's purpose understandable. However, it doesn't distinguish this tool from sibling multi_api_web_search, especially since the description itself says 'Multi-API'.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use web_search versus multi_api_web_search, and the sibling is not mentioned. The only usage signal is that 'hybrid' enables multi-engine consensus, which implies a mode choice but not when this tool should be preferred over an alternative.

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

Deploy Server