Skip to main content
Glama

Read one memory

get_memory
Read-onlyIdempotent

Retrieve one stored memory by ID, including its full content and linked topics, people, projects, and related memories.

Instructions

One Second Brain memory in full, with what it is linked to (topics, people, projects, related memories).

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": {
      "id": "<id>"
    },
    "name": "get_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe memory's id, from search_memories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description does add genuinely useful behavioral context by enumerating the linked data returned (topics, people, projects, related memories), which matters because there is no output schema. It does not say how missing/invalid ids behave, so the addition is real but partial.

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?

One sentence, front-loaded with the core resource, and every clause carries information (scope, fullness, linked entities). The lack of a leading verb makes it slightly less scannable than it could be, but nothing is wasted.

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?

For a one-parameter read tool with full annotation coverage, the description covers the essentials: what is fetched and what comes back with it, compensating for the absent output schema. Only failure behavior for a bad id is left uncovered, which is a minor gap at this complexity.

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% with a single required id whose meaning and provenance ('from search_memories') are documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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 names a specific resource and scope: a single ('One') Second Brain memory retrieved 'in full', which implicitly contrasts with the plural results of search_memories. The word 'One' does the sibling differentiation, but the phrasing is a noun fragment rather than a verb+resource statement, so the action is inferred rather than declared.

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: the single-memory framing suggests this is the follow-up to a search, but the description never says when to prefer it over search_memories or what to do if the id is unknown. The chaining hint ('from search_memories') lives only in the schema, not in the description.

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