Skip to main content
Glama

Search second brain

second_brain_search
Read-only

Search long-term memory for user preferences, project history, prior decisions, tools, and recurring workflows before answering or acting; review returned notes before consequential use.

Instructions

Search long-term memory before answering or acting on user preferences, project history, prior decisions, tools, or recurring workflows. Results are candidates; read the note before consequential use.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results; default 5.
queryYesNatural-language query or keywords.
scopesNoDefault: knowledge and topics. reviews and sources are opt-in.

Output Schema

NameRequiredDescriptionDefault
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond that by warning that results are candidates only and must be verified by reading the note before consequential use, which tells the agent about result reliability. It says nothing about ranking or how many candidates are returned, though limit is defaulted in the schema.

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 sentences, both earning their place: the first covers when to search and over what, the second front-loads the critical caveat about treating results as candidates. No filler or restatement of the name.

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?

The tool has annotations, an output schema, and full parameter documentation, so the description only needs to carry the when and the caveat, both of which it does. A brief note on whether results include note identifiers for the follow-up read would make it fully self-sufficient.

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 coverage is 100%, so query, limit, and scopes are already fully documented, including defaults and the opt-in status of reviews and sources. The description adds no meaning beyond the schema, which is the expected baseline-3 outcome when the schema does the heavy lifting.

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 ('Search long-term memory') plus the scope of what is searchable, which is enough to distinguish it from second_brain_capture or second_brain_read. It stops short of explicitly contrasting itself with the closest retrieval sibling, second_brain_recall_experience, so a 4 rather than a 5.

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?

It states a clear when-to-use trigger: before answering or acting on user preferences, project history, prior decisions, tools, or recurring workflows. The second sentence implicitly routes the agent onward to a read step for consequential use, but no exclusion or explicit alternative (e.g. when to prefer recall_experience or core_context) is named.

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