Skip to main content
Glama

web_search

Search the web without API keys, automatically falling back between engines if one fails. Returns titles, URLs, and snippets for OSINT research.

Instructions

Search the web (keyless) with automatic engine fallback.

Tries DuckDuckGo HTML first, then the Lite endpoint. Returns titles, URLs and snippets; failures report which engines were tried.

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

NameRequiredDescriptionDefault
queryYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the fallback chain (DuckDuckGo HTML then Lite), what is returned, and that failures report which engines were tried. It omits rate limits, result-content limitations, and whether cancellation/retry is possible, which keeps it from a 5.

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?

Three short sentences, front-loaded with the core action and differentiator, then fallback order, then return/failure shape. No filler and nothing repeated from the schema.

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 two-parameter read tool with no output schema, the description adequately covers return shape and failure behavior. However, the undocumented max_results parameter and unspecified result-count limits leave a real gap given 0% schema coverage.

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% for both parameters: neither "query" nor "max_results" is explained in the schema. The description compensates only indirectly by listing what a result contains, and never mentions max_results, its default of 10, or any upper bound, leaving the caller to guess.

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?

States a specific verb and resource ("Search the web") plus a differentiating trait ("keyless") that separates it from browser- or API-key-based search siblings. It does not explicitly name an alternative sibling, but the scope is unambiguous.

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?

"Keyless" implies the usage context (works without credentials/setup), which is implied guidance rather than explicit direction. There is no statement of when this should be preferred over alternatives such as browser_search, nor any exclusion or limitation on query types.

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