Skip to main content
Glama

Search the web

search
Read-only

Find ranked web links with titles and text for a query; refine by recency, locale, domains, and depth. Use extract for known URLs or investigate further.

Instructions

Search the web: ranked links with titles and text, in seconds; free if keyless, else billed. Use extract for a known URL, research to investigate. Higher effort costs more; leave it unset unless needed. For a login or form, suggest browser_open. data_apis: vendor APIs for call_vendor; offer one if it beats the pages.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to search for.
effortNoHigher costs more and takes longer: leave it unset unless needed.
localeNoLanguage code, e.g. 'en'.
countryNoCountry code for geo-targeting, e.g. 'US'.
recencyNoOnly sources dated within this.
providerNo
data_apisNoAlso list matching vendor data APIs under `data_apis`, free and never run; `call_vendor` runs one. On by default.
max_resultsNoUnset, the backend's default; 5 to 10 suit most.
search_depthNoText per result: 'lite' a snippet (~500 characters), 'fast' a few thousand, 'deep' the whole page, slowest. Unset, the backend's own default; a backend that cannot return a level's size refuses it.
data_apis_onlyNoThe data APIs alone, no web call; takes only `max_results`.
configured_onlyNoOnly data APIs whose credentials are set here.
exclude_domainsNoDrop results from these domains.
include_domainsNoRestrict results to these domains.

Output Schema

NameRequiredDescriptionDefault
noteNo
answerNo
handleYes
resultsNo
providerNo
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds cost and latency context the annotations cannot carry — "in seconds", "free if keyless, else billed", effort raising cost, and `data_apis` being free and never executed. It stops short of quantifying billing or describing rate limits or failure modes, so the cost/risk picture is directionally clear but not precise.

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?

Purpose and cost model are front-loaded in the first clause, and each subsequent fragment routes to a specific sibling, so almost every phrase earns its place. The style is telegraphic, with semicolon-joined notes that repeat schema wording for `effort` and `data_apis` rather than adding to it.

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?

With an output schema present, return values need no prose, and the description covers routing, cost, latency, and the `data_apis` hand-off for a 13-parameter tool. The gap is `provider` (a four-value enum with no description anywhere) and no mention of the `data_apis_only`/`configured_only` modes, which an agent must discover from the schema alone.

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 92%, so nearly every parameter is already documented; the description mostly restates it ("Higher `effort` costs more; leave it unset unless needed" duplicates the schema wording verbatim). The one genuinely unannotated parameter, `provider`, is not explained in either the schema or the description, so no compensating value is added there.

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 opening clause gives a specific verb and resource ("Search the web") and immediately characterizes the shape of the result ("ranked links with titles and text, in seconds"), so an agent knows both what it does and what it returns. It then explicitly contrasts itself with `extract` (known URL), `research` (investigate), and `browser_open` (login/form), making it distinguishable from siblings without opening any schema.

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

Usage Guidelines5/5

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

Alternatives are named with the exact condition that selects each: `extract` for a known URL, `research` to investigate, `browser_open` for a login or form, `call_vendor` for a returned data API. It also gives a guidance rule for the `effort` parameter ("leave it unset unless needed") and a recommendation for surfacing `data_apis` ("offer one if it beats the pages").

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