Skip to main content
Glama

Recall verified second-brain experiences

second_brain_recall_experience
Read-only

Search prior task outcomes and lesson candidates by query, task type, project, outcome, or error signature; get candidates with evidence levels and a receipt.

Instructions

Retrieve prior task outcomes and lesson candidates by query, task type, project, outcome, or error signature. Results are candidates with evidence levels and a receipt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "second_brain_recall_experience"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
outcomeNo
projectNo
taskTypeNo
errorSignatureNo

Output Schema

NameRequiredDescriptionDefault
receiptYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 the safety profile is covered. The description adds meaningful behavioral context beyond that: results are candidates with evidence levels and a receipt, which tells the agent the output is not authoritative recall. It does not discuss pagination, limit defaults, or ordering, but with annotations present the bar is lower.

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?

The description is two compact sentences with the core action and filter dimensions front-loaded. The second sentence adds an important result caveat without unnecessary wording. Every phrase contributes to understanding the tool.

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 return-value details need not be explained, and read-only annotations cover the safety profile. However, for a six-parameter recall tool with 0% schema description coverage, the description leaves important gaps: how filters combine, what limit defaults to, and what 'error signature' means in practice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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. It lists query, task type, project, outcome, and error signature, but these are essentially the schema property names with no added semantics about matching behavior, combination logic, or format. The limit parameter is not mentioned at all, and no filter is explained beyond its label.

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 states a specific verb and resource: retrieve prior task outcomes and lesson candidates. It also names the filter dimensions, so the tool's purpose is clear without opening the schema. It does not, however, explicitly distinguish this recall tool from closely related siblings such as second_brain_search or second_brain_read.

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 by 'Retrieve prior task outcomes and lesson candidates,' which tells an agent this is for recalling past experience. There is no explicit when-to-use guidance, no when-not-to-use guidance, and no routing to alternative tools for similar retrieval needs.

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