Skip to main content
Glama

Wake

Search the site's pages

search
Read-only

Find pages on this site by topic. Returns titles, descriptions and URLs; read one with read_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": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many pages to return (default 8).
queryYesWhat you are looking for, in a few words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is to add context beyond that. It does: it discloses the return fields (titles, descriptions, URLs) and that results are page-level links rather than content, which matters because no output schema exists. It does not discuss ranking, matching behavior, or empty-result handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two compact sentences: the first states purpose and scope, the second states the return shape and the next action. Every clause carries information and the routing tip is placed where it is most useful — after the result description.

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 two-parameter read-only search tool with an annotated safety profile and a short description, this covers purpose, return fields, and the follow-up action. Minor gaps remain — result ordering, behavior on no matches — but nothing needed to call it correctly is absent.

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 both parameters are already documented including the limit default and maximum. The description reinforces that the query is topical ("by topic") but adds no syntax or formatting guidance beyond the schema, 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?

"Find pages on this site by topic" gives a specific verb (find), resource (pages), and scope (this site, by topic), and states the return shape (titles, descriptions, URLs). It also names read_page as the follow-up tool, so an agent can separate discovery from retrieval without opening either 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?

The definition implicitly establishes its condition — use it when you only know a topic, not a page — and explicitly routes the agent to read_page to fetch a specific result. There are no explicit when-not-to-use exclusions, so it falls short of a 5.

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