Skip to main content
Glama

search_brain

Find notes by exact keywords and semantic meaning in one merged ranking, filter by tags or folder, and return relevance-ranked note paths with short excerpts.

Instructions

Find notes by exact words and by meaning at once: a keyword ranking and an embedding ranking are merged into one list. Narrow it with frontmatter tags or a folder. Each result is a note path with a short excerpt, most relevant first.

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_brain"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
limitNo
queryYes
folderNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the whole behavioral burden. It does disclose the ranking mechanism (two rankings merged), the effect of the filters ('Narrow it'), the result shape (note path plus short excerpt), and the ordering (most relevant first), which is genuinely useful. It says nothing about read-only semantics, latency/cost of the embedding pass, whether the index must be fresh, or pagination behavior beyond the schema default.

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?

Three short sentences, front-loaded with the core differentiator, then narrowing controls, then result format. Nothing is redundant. The middle sentence is slightly clipped ('Narrow it with frontmatter tags or a folder'), which trades a little precision for compactness.

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?

An output schema exists, so the description need not explain return values, though it does so briefly and accurately. For a 4-parameter tool with zero schema description coverage and no annotations, the missing coverage of 'limit' and the absence of any note about result-set size or index freshness leave a moderate gap.

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 has to compensate, and it largely does: it explains that 'query' is matched both lexically and semantically, that 'tags' are frontmatter tags, and that 'folder' scopes the search. The 'limit' parameter (default 20) is never mentioned, which is the one real gap in an otherwise strong explanation of four undocumented parameters.

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?

The description gives a specific verb-and-resource with its distinguishing mechanism: hybrid retrieval merging a keyword ranking and an embedding ranking into one list. That is materially different from a plain keyword or plain semantic sibling, so an agent can tell what makes this tool unique without opening the schema.

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 implied rather than stated: 'exact words and by meaning at once' suggests this is the tool to pick when either pure keyword or pure semantic search would be insufficient. However, it names no alternative among the many sibling retrieval tools (query_notes, recall_bundle, related_notes, list_recent) and gives no exclusions or prerequisites, leaving the selection decision partly to inference.

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