Skip to main content
Glama

Get one memory by id

get_memory
Read-only

Fetch a stored memory by its ID to inspect its value, status, scope, confidence, superseded links, and metadata before acting on it.

Instructions

Fetch one memory by its id (the #id shown by list_memories) — its value, status, scope, confidence, what it supersedes, and any metadata.

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

Input Schema

NameRequiredDescriptionDefault
run_idNo
user_idNodefault
agent_idNo
memory_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.6/5.0
Behavior3/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 the returned field inventory (status, confidence, what it supersedes), but says nothing about memory scoping behavior via run_id/user_id/agent_id or what happens when the id is unknown — meaningful gaps for a lookup tool in a scoped store.

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?

A single front-loaded sentence with the key selector in the opening clause and no redundant or filler wording.

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 enumerating returned fields is arguably redundant, and the description omits the scoping parameters and not-found behavior that an agent needs to call this correctly. Adequate for the happy path, incomplete for the parameter surface.

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% across 4 parameters, so the description must carry the load. It explains memory_id well (an integer id as displayed by `list_memories`), but leaves run_id, user_id, and agent_id — the scope filters that determine which memory is actually retrievable — entirely undefined in both schema and prose.

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?

States a specific verb and resource ("Fetch one memory") plus a precise selector ("by its id"), and ties the id to `list_memories`, which distinguishes this point lookup from the listing/semantic-retrieval siblings.

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?

The parenthetical "the `#id` shown by `list_memories`" implies the workflow (list first, then fetch by id), but there is no explicit when-to-use/when-not guidance and no comparison to alternatives such as recall or safe_recall for lookup-by-meaning.

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