Skip to main content
Glama

read_search

Read-only

Search LeafWiki pages by title, content, or tags to find relevant results with excerpts, ordered by best match.

Instructions

Full-text search over page titles, content and tags, best match first, with excerpts.

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": "read_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 20
queryYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish this as a safe, closed-world read operation, so the description only needs to add further context. It does add useful ranking behavior ('best match first') and the fact that excerpts come back; however, it says nothing about result counts, pagination behavior, or what happens with zero matches, which is what an agent would need in order to call it correctly.

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?

It is a single compact sentence with the resource and scope front-loaded, followed by ordering and output details. There is no filler; every clause carries information.

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

Completeness3/5

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

For a read-only search with three flat parameters and no output schema, the description covers the essentials of what is searched and how results are ordered. It is nevertheless thin on how to page through large result sets and on query syntax, both of which matter for a limit/offset search tool with a maximum page size of 100.

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 only 33%: the required query parameter has no schema description at all, and offset has none, while limit only carries a default. The description partially compensates by revealing what query matches against (titles, content, tags), which is the key semantic, but it leaves query syntax and offset paging unexplained.

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 uses a specific verb and resource ('Full-text search over page titles, content and tags') and clarifies scope by naming the searched fields, ranking order ('best match first') and output shape ('with excerpts'). It does not name any sibling, so the agent must infer that it should prefer read_find_title for title-only lookups, but the field scope it states already implies a broader search.

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?

The description describes what the tool is and implies usage, but supplies no explicit when-to-use or when-not-to-use guidance and does not reference alternatives such as read_find_title or read_pages_by_tags. The only contextual cue is that it spans titles, content and tags, which suggests it is the general search entry point.

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