Skip to main content
Glama

Search Web

search_web
Read-onlyIdempotent

Searches the web for current information on dishes, ingredients, techniques, or regional variations when bundled datasets lack details.

Instructions

Search the web for current information about a dish, ingredient, technique, or regional variation. Returns search result objects with titles, links, and snippets. Use when the bundled datasets lack information and live web search is needed. Pass query from the search terms.

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_web"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query

Output Schema

NameRequiredDescriptionDefault
noteNo
errorNo
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the safety profile is fully carried by structured data. The description adds the result-object shape but says nothing about result count, ranking, freshness, or network/auth failure behavior for an open-world call. With annotations doing the heavy lifting, this is adequate but not rich.

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 purpose then return shape then usage condition, with no filler. The return-shape sentence partially duplicates the existing output schema, which is the main slack.

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 single-parameter read-only web search with a full output schema and rich annotations, the description covers what it does, when to reach for it, and what it returns. Nothing an agent needs in order to invoke it correctly is missing.

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?

Only one parameter exists and it is fully documented in the schema ("Search query", 1-500 chars), so the baseline is 3. "Pass query from the search terms" adds little beyond restating that the query is passed through; no guidance on query construction, breadth, or phrasing that would improve result quality.

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 ("Search the web") plus a tightly scoped domain of resources ("dish, ingredient, technique, or regional variation"), which distinguishes it from dataset-internal siblings. It also names the return shape, so an agent knows what comes back without opening the output schema.

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

Usage Guidelines4/5

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

Gives a clear trigger condition: use when the bundled datasets lack information and live web search is needed. It stops short of naming a specific alternative sibling or stating when-not to use it (e.g., prefer local datasets for canonical/known dishes), so it is clear context rather than a full routing rule.

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