Skip to main content
Glama

Web search

web_search
Read-only

Search the web via Google. Returns titles, URLs, and snippets for any query. Useful for research, fact-checking, and finding current information. Costs $0.01 USDC per call.

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
queryYesSearch query
numResultsNoNumber of results to return (max 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description's real contribution is the pricing disclosure — '$0.01 USDC per call' — which is essential behavioral context an agent cannot get from structured fields. It also describes the return payload, though it omits rate limits or failure/empty-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?

Four short sentences, front-loaded with the action and result shape, then use cases, then cost. Each sentence carries information, though the 'research, fact-checking' sentence is the weakest and borders on filler.

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

Completeness5/5

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

For a two-parameter, non-destructive read tool, the description covers action, source (Google), return fields, cost, and typical use. No output schema exists, yet the description still explains the return shape, leaving nothing an agent needs in order to call it correctly.

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 'query' and 'numResults' (with default 10 and max 20) are already fully documented. The description adds nothing parameter-specific beyond the vague phrase 'for any query', so baseline 3 applies.

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 via Google') plus the exact shape of what comes back ('titles, URLs, and snippets'), which an agent can use to distinguish it from web_scrape. It stops short of explicitly naming that sibling, so differentiation is inferential rather than stated.

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?

'Useful for research, fact-checking, and finding current information' gives implied usage contexts, but there are no exclusions and no routing advice toward web_scrape (full page content) versus this tool (snippets only) — the most likely sibling confusion in this catalog.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources