Skip to main content
Glama
Sign In
SecondBrain

SecondBrain

by no-carve-only-pizza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_candidate_get

Retrieve one memory candidate by its ID from SecondBrain so agents can inspect or validate captured context before relying on it.

Instructions

Get one memory candidate by ID.

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": {
      "candidate_id": "<candidate_id>"
    },
    "name": "memory_candidate_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidate_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing about behavior. It does not say whether the read is safe/non-mutating, what happens when the candidate_id does not exist (error vs empty), or whether pending/expired candidates are visible. 'Get' implies a read, but that is inference, not disclosure.

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?

A single short sentence with no padding and the key constraint ('by ID') front-loaded. It is efficient, though its brevity is partly under-specification rather than disciplined concision.

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?

For a trivial one-parameter lookup with no output schema, this is close to the minimum viable. It is missing error/not-found behavior and any definition of what a 'candidate' is in the lifecycle (create/list/approve/reject/expire), which the sibling set shows is a meaningful distinction.

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?

One required parameter with 0% schema description coverage, so the description must compensate. 'By ID' confirms candidate_id is an identifier, but adds no format, expected value, or source for that ID (e.g., from memory_candidate_list). Marginal added value over the schema's string type.

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 ('Get one memory candidate by ID'), which is clearer than a bare name restatement. It implicitly separates itself from memory_candidate_list (single by ID vs list), but never distinguishes itself from the sibling memory_get, so an agent must guess which retrieval path applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no mention of alternatives such as memory_candidate_list or memory_get. The only hint is the phrase 'by ID', leaving the agent to infer the retrieval context entirely.

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