Skip to main content
Glama

get_memory

Retrieve the full text of specific memories by ID so you can inspect details referenced in project context, recall, or related results.

Instructions

Fetch the full text of specific memories by id (ids come from project_context, recall, or related).

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

Input Schema

NameRequiredDescriptionDefault
idsYesMemory ids (max 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose that the return is the complete text rather than an excerpt, which is the key behavioral fact here. It says nothing about what happens with unknown or deleted ids, batching behavior, or failure modes, leaving real gaps for a mutation-free but lookup-heavy tool.

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?

One sentence, front-loaded with the operation and resource, with the qualifier parenthesized rather than buried. Nothing is wasted and nothing essential is deferred.

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 single-parameter, read-only lookup with no output schema, the description covers the purpose, the input source, and the granularity of the return value. Only edge-case behavior for missing ids is left unstated, which is minor 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% and the single parameter already documents its type and the max-20 cap, so the description correctly does not repeat that. Its only added value is naming upstream tools that produce valid ids, which is modest but genuine.

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?

Uses a specific verb+resource ("Fetch the full text of specific memories by id") and differentiates itself by scope: this is the full-text retrieval path as opposed to the sibling tools that surface ids. It stops short of explicitly naming which sibling to use instead when full text is not needed, so it is clear but not fully disambiguating.

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?

The parenthetical states a real precondition — ids must come from project_context, recall, or related — which effectively encodes the two-step workflow an agent must follow. There is no explicit when-not guidance, but the precondition is enough to place the tool correctly in a sequence.

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