Skip to main content
Glama

get_memory

Read-onlyIdempotent

Retrieves the full content of a single memory by its exact key, with optional flags to include archived or expired entries hidden from recall.

Instructions

Full text of ONE memory by exact key (the key field recall returns). Returns the full content of an entry whose recall result ends with the … cut marker. Errors if no entry has exactly that key. Archived and expired entries are hidden unless include_archived / include_expired is set.

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

Input Schema

NameRequiredDescriptionDefault
keyYesExact memory key, as returned by recall.
scopeNoFilter by scope: workspace, project, agent, or all (default).
project_idNoProject of a project-scoped entry, if the key exists in several.
include_expiredNoAlso look among memories past their expires_at (default false). An expired entry is hidden from recall and get_memory the moment it expires and stays readable with this flag until the background cleanup (every 6 h) physically deletes it 7 days after expiry. To take an entry out of recall so it can be brought back, use archive_memory instead of a short expires_at.
include_archivedNoAlso look among archived memories (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.7
    • addedInput schema / properties / include_expired
      Added value: +{
      +  "default": false,
      +  "description": "Also look among memories past their expires_at (default false). An expired entry is hidden from recall and get_memory the moment it expires and stays readable with this flag until the background cleanup (every 6 h) physically deletes it 7 days after expiry. To take an entry out of recall so it can be brought back, use archive_memory instead of a short expires_at.",
      +  "type": "boolean"
      +}
  2. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: hidden archived/expired entries unless flags are set, and an error (not an empty result) on key miss. It does not describe output shape or whether content is truncated, but the key behavioral surprise — errors and hidden entries — is disclosed.

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?

Four tight sentences, front-loaded with the core purpose and the recall-marker trigger, then the error condition, then the visibility caveat. No filler, though the final sentence packs two flags and one alternative-tool recommendation into one line, which is slightly dense.

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 read tool with full schema coverage and no output schema, the description covers selection, the trigger condition, error behavior, and visibility defaults. The remaining gap is return-format detail (is content raw text? any metadata?), which an agent might want but can discover from the response.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns extra by explaining why include_archived/include_expired matter (the entry would otherwise be invisible) and by tying `key` to recall's output field. It does not clarify how `scope` and `project_id` interact when a key exists in several projects, which the schema only gestures at.

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 ('Full text of ONE memory by exact key') and explicitly scopes it to the single-entry case, distinguishing it from recall which returns multiple results. The parenthetical tying the key to 'the `key` field recall returns' makes the relationship to the sibling unambiguous.

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

Usage Guidelines5/5

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

Explicitly says when to use it: when a recall result ends with the '…' cut marker and the full content is needed. It also names the failure mode ('Errors if no entry has exactly that key') and points to archive_memory versus short expires_at as the alternative for hiding entries. That is when-to-use, when-not-to-use, and alternative routing in one short paragraph.

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