Skip to main content
Glama

search

Read-only

Full-text search over your brain and the shared ones, 2-4 keywords. Returns paths, dates and matching lines. Excerpts are not the note: read_file before answering. Hits below Maybe related match only some words; below Similar in meaning none, found by meaning (on plans that include it); below Inside attachments the words are inside PDF, Word, Excel… files. ↳ links to = notes that note links with [[...]]. path narrows to a branch.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly annotations, the description discloses exactly what comes back (paths, dates, matching lines) and decodes the result sections: `Maybe related`, `Similar in meaning`, `Inside attachments`, and `↳ links to`. That is genuine behavioral context an agent cannot get from annotations or schema, including the caveat that snippets are not the note itself.

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 purpose and return shape, then a compact decoder for each result section; nearly every sentence carries information. The heavy backtick labeling and ellipsis ('PDF, Word, Excel…') make it denser to parse than ideal, but no sentence is filler.

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?

With no output schema, the description compensates well by explaining result groups, the links relation, and the required follow-up read. It omits result limits, ranking/pagination behavior, and how multiple keywords combine, which are the remaining gaps for a search tool.

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 must carry parameter meaning, and it does: `query` is framed as 2-4 keywords and `path` is described as narrowing to a branch. The `path` explanation is brief and doesn't specify format (folder prefix vs exact note path), leaving a minor gap.

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?

States a specific verb and resource ('Full-text search over your brain and the shared ones') plus a query-shape hint ('2-4 keywords'). It does not explicitly distinguish itself from neighboring search tools like app_search or search_mentions, so sibling differentiation is partial rather than explicit.

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?

Gives a concrete downstream rule ('read_file before answering') and explains that `path` narrows to a branch, which tells the agent how to scope a search. It stops short of naming when to prefer an alternative search tool, so exclusion guidance is absent.

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