Skip to main content
Glama

Search everything

search_site
Read-onlyIdempotent

Searches the whole publication at once and says what kind each hit is: news articles, First Light items, entity records, projects, source documents and tracker pages. This is the broad search — prefer it when the question is not already about one kind of thing, because search_articles and the other per-kind tools look only in their own kind. Matching ignores case AND accents, so "Male" finds "Malé"; a query wrapped in slashes (/min(istry|ister)/) is a regular expression. Every hit carries the canonical URL to cite. Searches the most recent 400 stories and 45 First Light editions, and all reference records. Paginates: when more results remain, the structured answer has a nextCursor (absent on the last page). To continue, call this tool again with the same arguments and cursor set to that value. The cursor moves every kind on together: each page shows the next limit hits of each kind.

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": {
      "q": "<q>"
    },
    "name": "search_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWords to look for, or /a regular expression/.
langNoen (English) or dv (Dhivehi).en
limitNoHits to return per kind (1-25, default 8).
cursorNoContinue a previous result: the nextCursor it returned, unchanged. Only valid with the same other arguments (limit may differ).

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYesEvery hit across all kinds, not just this page.
groupsYes
nextCursorNoOpaque cursor for the next page: pass it back as the cursor argument, with the same other arguments. Absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses concrete behavior: case- and accent-insensitive matching with an example ("Male" finds "Malé"), slash-wrapped regex syntax, coverage boundaries (most recent 400 stories, 45 First Light editions, all reference records), and that every hit carries a citable canonical URL. It also explains pagination mechanics that annotations cannot express.

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-loaded with the broad-search positioning and decision rule before mechanics, and nearly every sentence carries information. It is on the long side for a single paragraph, with the coverage limits and pagination details stacked at the end, but nothing is redundant 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?

Even though an output schema exists, the description still supplies what an agent needs to interpret it: nextCursor presence/absence, how to resume, and the fact that results are per-kind buckets. Coverage limits also set correct expectations about result completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description adds real meaning: q accepts accent-insensitive terms or /regex/, and cursor must be combined with identical arguments except limit. The non-obvious detail that the cursor advances every kind together and each page returns the next `limit` hits of each kind goes beyond the per-parameter schema text.

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 (searches) and scope (the whole publication) and enumerates the kinds of hits returned: news articles, First Light items, entity records, projects, source documents, tracker pages. It explicitly positions itself as the broad counterpart to search_articles and the other per-kind tools, so an agent can distinguish it from siblings without opening any schema.

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 a direct decision rule: prefer this when the question is not already about one kind of thing, because per-kind tools look only in their own kind. That names the alternatives and the condition that selects them, leaving nothing to inference.

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