Skip to main content
Glama

ninerouter_web_search

Search the public web, news, or X posts through a configured 9Router provider. Specify a query, search type, language, or time range to retrieve filtered results for research and monitoring.

Instructions

Search public web, news, or X using a configured 9Router search provider.

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": "ninerouter_web_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel ID or combo from ninerouter_list_models.
queryYes
countryNo
optionsNoAdditional fields supported by the selected 9Router endpoint.
languageNo
providerNoProvider alias. Supply either provider or model.
time_rangeNo
max_resultsNo
search_typeNo
domain_filterNo
provider_optionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations declare openWorldHint=true, readOnlyHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only the notion of a configured backend; it says nothing about cost/credit consumption (which readOnlyHint=false hints at), rate limits, or result behavior.

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?

A single front-loaded sentence with no wasted words. Its brevity is appropriate for the phrasing but leaves no room to convey the semantics the 11 parameters need.

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

Completeness2/5

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

For an 11-parameter, open-world tool with no output schema and low schema description coverage, the description is far too thin. An agent would not know how to populate the search filters or what to expect in the response.

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 coverage is only 27% across 11 parameters, so the description must compensate, and it largely does not. Mentioning "web, news, or X" implicitly maps to the search_type enum, but country, language, time_range, max_results, domain_filter, model, provider, and the options bags are left undocumented.

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 names a specific verb ("Search") and specifies the target resources ("public web, news, or X"). It clearly distinguishes a search operation from the sibling ninerouter_web_fetch, though it never states the distinction explicitly.

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?

It hints at a prerequisite with "a configured 9Router search provider," but gives no explicit when-to-use versus ninerouter_web_fetch, no exclusions, and no guidance on required setup or failure modes when no provider is configured.

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