Skip to main content
Glama

Search the web

search
Read-only

One web search through POST /v1/search: titles, URLs, snippets and publish dates, up to 10 results, optionally only from the last day, week, month or year. Billed as one search to the key in the MCP request's Authorization header (the price in GET /v1/catalog server_tools); a search that fails is not charged.

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, up to 400 characters.
freshnessNoOnly pages published inside this window.
max_resultsNo1 to 10 results. Default 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, non-idempotent, non-destructive, so the description correctly spends its words elsewhere: it discloses the billing model (one search charged to the Authorization key, failed searches not charged) and points to where pricing lives. That is real value beyond the annotations; it misses only things like rate limits or latency expectations, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loads the core action and result shape before moving to cost, with no filler. It is heavy for one sentence, but every clause earns its place and nothing is redundant.

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?

For a 3-parameter tool with no output schema, the description covers return fields, the result cap, the pricing/failure-charging behavior, and the auth source for billing — enough to call correctly. The only gap is whether results are paginated or what exactly a failure looks like, which is minor.

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 the parameters are already documented; the description only restates the 10-result cap and the freshness windows (day/week/month/year). It adds the useful nuance that freshness means 'only pages published inside this window,' but that is largely a rewording of the schema's enum description, 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 action (web search via POST /v1/search) and even names the return fields — titles, URLs, snippets, publish dates — which makes the tool's output shape immediately clear. No sibling is a competing search tool, but the description doesn't explicitly distinguish itself from alternatives such as chat or generate, so it stops short of a 5.

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?

Phrasing it as 'One web search' implies a single-shot query with no pagination or iteration, which is useful, and the freshness option hints at recency-restricted use cases. However, there is no explicit when-to-use / when-not-to-use guidance relative to siblings like chat or generate, so guidance is only implied.

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.