Skip to main content
Glama
seeker

seeker

by bottercode

web_search

Search a web index by query to return page titles, URLs, crawl dates, highlights, and opening content snippets for research, verification, or discovery.

Instructions

Search the web index. Returns title, url, crawl date, relevant highlights and the start of each page.

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
num_resultsNo
max_charactersNo
exclude_domainsNo
include_domainsNo
start_published_dateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It states what fields come back, but says nothing about cost, rate limits, query syntax, or the fact that results are truncated previews rather than full pages, and the return-value detail it does give is largely duplicated by the existing output schema.

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?

Two tight sentences with no filler, and the core action is front-loaded before the return-value detail. Nothing is redundant, though the second sentence spends the limited space on information the output schema already supplies.

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

Completeness1/5

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

Given no annotations, six undocumented parameters, and a meaningful sibling set, the description is far too thin: it omits the guidance that would actually help an agent choose and invoke it correctly. It instead restates return fields that the output schema already defines.

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% across 6 parameters, and the description never explains query syntax, what num_results controls, or how include_domains and exclude_domains interact. The phrase 'start of each page' faintly hints at truncation controlled by max_characters, but start_published_date and the domain filters are entirely undocumented in both places.

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?

The description gives a specific verb and resource ('Search the web index') and a concrete sense of scope, which is immediately distinguishable from a generic utility. It does not, however, differentiate itself from the siblings find_similar and get_contents, which is the main gap at this level.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, nor any mention of the alternatives (e.g. use get_contents for full page text rather than the truncated snippets returned here). Usage is only implied by the verb 'search'.

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

Deploy Server

Other Tools