Skip to main content
Glama

Get a memory by ID

amber_get_memory
Read-onlyIdempotent

Retrieve a single memory by ID with full, untruncated content and metadata. Use it after a search returns a truncated result, or when you have a memory ID and need the complete text.

Instructions

Retrieve a single memory by its ID with full, untruncated content. Use this after amber_search_memories when a result's content was truncated (indicated by truncated: true), or when you have a memory_id from a previous interaction and need the complete text.

Returns the memory with its full content, metadata (if any), topic names (if any), and created_at timestamp. Resolves a memory by id whether it is active OR in the trash -- a non-empty deleted_at marks a trashed one (restore it with amber_restore_memory). Returns code: not_found only if no memory with that id exists at all. Read-only -- does not modify the memory. Not rate-limited. Requires an active subscription.

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": "amber_get_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_idYesUUID of the target memory. Found in `amber_store_memory` task results, `amber_search_memories` result items, or `amber_list_memories` pages.

Output Schema

NameRequiredDescriptionDefault
memoryYesThe memory: full content, its `subject` (a single string, not a list), metadata, topic names, and timestamps. It does NOT carry the stored variants -- those are search-time phrasings, not part of the record. A memory in the trash is returned too, with its deletion time set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "memory": {
      +      "additionalProperties": {},
      +      "description": "The memory: full content, its `subject` (a single string, not a list), metadata, topic names, and timestamps. It does NOT carry the stored variants -- those are search-time phrasings, not part of the record. A memory in the trash is returned too, with its deletion time set.",
      +      "properties": {
      +        "content": {
      +          "description": "The fact itself, exactly as stored.",
      +          "type": "string"
      +        },
      +        "created_at": {
      +          "description": "ISO 8601 time the memory was stored. Not when the event happened: that is event_start.",
      +          "type": "string"
      +        },
      +        "deleted_at": {
      +          "description": "ISO 8601 time the memory was moved to the trash. Absent or empty for a live memory; present means amber_restore_memory can bring it back.",
      +          "type": "string"
      +        },
      +        "event_end": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "ISO 8601 datetime the fact's event ended, or null."
      +        },
      +        "event_start": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "ISO 8601 datetime the fact's event began, or null when the fact has no event date."
      +        },
      +        "memory_id": {
      +          "description": "The memory's id. Pass it to amber_get_memory, amber_update_memory, amber_delete_memory or amber_restore_memory.",
      +          "type": "string"
      +        },
      +        "metadata": {
      +          "additionalProperties": {},
      +          "description": "The caller's own exact-match filter values, as stored (a flat object). Absent or empty when none were set.",
      +          "propertyNames": {
      +            "type": "string"
      +          },
      +          "type": "object"
      +        },
      +        "subject": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Who this memory is about -- a named subject like \"patrick\" or \"patrick's father\", or null if not yet determined."
      +        },
      +        "subjects": {
      +          "description": "The same people as an ARRAY, which is the shape every tool ACCEPTS -- pass it straight back as `subjects` on a search. `subject` is the comma-joined rendering of the same value and matches nothing if passed as an argument; absent here means the memory has no attribution.",
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "topics": {
      +          "description": "The topic names this memory is filed under (at most 3 for a new store).",
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "memory_id",
      +        "content"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "memory"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv1.1.4
    • changedInput schema / properties / memory_id / description
      Previous value: -"UUID of the memory to retrieve. Use this to fetch full content after seeing a truncated search result, or to revisit a known memory. Invalid or trashed IDs return `code: not_found`."New value: +"UUID of the target memory. Found in `amber_store_memory` task results, `amber_search_memories` result items, or `amber_list_memories` pages."
  3. Changed1 schema field changedv1.1.3
    • changedInput schema / properties / memory_id / description
      Previous value: -"The unique memory ID (UUID format). Obtained from `amber_store_memory` results, `amber_search_memories` results, or `amber_list_memories` output."New value: +"UUID of the memory to retrieve. Use this to fetch full content after seeing a truncated search result, or to revisit a known memory. Invalid or trashed IDs return `code: not_found`."
  4. Changed1 schema field changedv1.1.1
    • changedInput schema / properties / memory_id / description
      Previous value: -"The memory ID, as returned by `amber_store_memory` or included in search results."New value: +"The unique memory ID (UUID format). Obtained from `amber_store_memory` results, `amber_search_memories` results, or `amber_list_memories` output."
  5. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint:false, but the description goes further: it resolves IDs across active AND trashed memories, explains that a non-empty `deleted_at` marks a trashed record, documents the `code: not_found` failure case, and states it is not rate-limited but requires an active subscription. That is meaningful behavioral context beyond structured fields.

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?

Front-loaded with the purpose and the truncation trigger, then the return shape, then edge cases (trash, not_found, rate limit, subscription). No sentence is filler; each adds a distinct operational fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with an output schema and full annotations, this covers everything an agent needs: when to call it, what it returns (content, metadata, topics, created_at), how trashed records behave, and the failure mode. Nothing material is missing.

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 description coverage is 100% and the schema already tells the agent where memory_id comes from (store task results, search items, list pages). The description adds the truncation rationale for fetching by ID but no additional constraint on the ID format itself, so baseline 3 applies.

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+resource ('Retrieve a single memory by its ID') and immediately scopes it as 'full, untruncated content', which distinguishes it from the search/list siblings that truncate. An agent can tell exactly which tool fetches a complete record.

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 names the trigger condition: use after `amber_search_memories` when a result shows `truncated: true`, or when a memory_id is already known. It also names `amber_restore_memory` as the follow-up for trashed records, routing the agent correctly instead of guessing.

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