Skip to main content
Glama

Search the web

web_search
Read-onlyIdempotent

Search the public web and get the results a search engine lists: each page's title, address and a snippet. Use it for what Corridome's database does not hold: a company's own website, news, a person's profile, an issuer or sponsor with no record on file. Search the database first when the question is about a firm, fund, deal, company or person it could hold. A snippet is not the page: read a result with web_fetch before stating what it says. Members only.

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
queryYesWhat to search the web for, as you would type it into a search engine. Quote a name to match it exactly.
recencyNoOnly pages published in the last day, week, month or year.
max_resultsNoHow many results to return, 1 to 30. Ten is one page of results.
allowed_domainsNoOnly results from these sites, like ["sec.gov"].
blocked_domainsNoNo results from these sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, idempotent, non-destructive), yet the description adds genuinely new behavior: an authentication gate ("Members only") and the warning that a snippet is not the page, which prevents an agent from asserting page content from search output. It stops short of mentioning rate limits, cost, or result ordering, so it is strong but not exhaustive.

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?

Front-loads what the tool does and what it returns before the routing rules, with zero filler sentences. The one weak spot is the enumerative clause "a firm, fund, deal, company or person it could hold," which restates the sibling scope at more length than needed.

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?

With no output schema, the description compensates by describing the return fields (title, address, snippet) and their limits. Combined with the auth note and the web_fetch follow-up, an agent has everything needed to call it correctly and interpret the result.

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, recency, max_results, allowed_domains and blocked_domains are already fully documented with enums, bounds and defaults. The description adds no parameter-level detail beyond the schema (even the exact-match quoting tip is already in the query field description), so the baseline 3 applies.

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?

States a specific verb and resource ("Search the public web") and explicitly defines the return shape: each page's title, address and a snippet. It also carves out a distinct scope against the database-backed siblings by naming the content types those tools do not hold (company websites, news, profiles, issuers/sponsors with no record).

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?

Gives an explicit routing rule: search the database first when the question is about a firm, fund, deal, company or person it could hold, and use this only for what the database does not hold. It also names the follow-up tool and its condition — read a result with web_fetch before stating what it says.

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