Skip to main content
Glama

search

Read-onlyIdempotent

Locate Markdown notes containing every word in a query, rank matches by word frequency, and show up to three matching lines per page.

Instructions

Find pages containing all the words in the query (case-insensitive).

Results are ranked by how often the words occur and show up to three matching lines.

Args: query: One or more words; a page must contain every word to match. limit: Maximum number of pages to return (1 to 50).

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
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral detail beyond that: results are ranked by word frequency, snippets are capped at three matching lines, and matching is case-insensitive and conjunctive. It stops short of describing pagination or how sparse results can be when a query word is rare, which would be the next level of detail.

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?

The behavior statement is front-loaded in the first sentence and the parameter notes are compact. The phrase "One or more words" and the all-words-to-match rule are stated twice (body and Args), a minor redundancy, but nothing is padded or off-topic.

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 search tool with an output schema, the description covers query semantics, result ordering, and snippet cap, which is close to everything needed. The only meaningful gap is the absence of guidance relative to the sibling listing and reading tools, which matters for selection given the generic name "search".

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 description coverage is 0%, so the description carries the parameter burden and largely does: query is defined as one or more words that must ALL be present, and limit is bounded at 1 to 50. It omits the schema's default of 10, but the key semantic (AND-matching) is exactly what an agent needs to construct correct queries.

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 ("Find pages containing all the words") plus scope details like case-insensitivity and line-based results. It does not explicitly distinguish itself from siblings such as list_pages or read_page, so an agent must infer the keyword-search niche rather than being told it.

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?

Usage is only implied: the AND-matching semantics suggest this is for keyword lookup across page content rather than enumeration or retrieval. There is no explicit when-to-use statement, no guidance on choosing this over list_pages or read_page, and no mention of when search is a poor fit.

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