Skip to main content
Glama

Get memory

get_memory
Read-onlyIdempotent

Retrieve the full content and metadata of a memory by its UUID. Use after list_memories or recall to get the complete text, memory type, tags, collection, importance, and timestamp.

Instructions

Retrieve the full content and metadata of one memory by its UUID. Use after list_memories or recall returned a truncated preview and you need the complete text. Returns content, memory_type, tags, collection, importance, and the creation timestamp. Get the UUID from a prior list_memories or recall result. The workspace this memory belongs to is determined by its ID and echoed in resolved_workspace; optionally pass workspace: to confirm the memory belongs to that team workspace (errors if it does not).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYesUUID of the memory to retrieve.
workspaceNoTo operate on a team workspace, pass its exact name, slug, or ID (e.g. "Acme"). Omit — or pass "personal" — for your personal memory (default). Every response echoes resolved_workspace so you can confirm where the operation actually happened. If the user mentions a project or team name in their message, check the memory://workspaces resource (or call list_collections) for the exact matching name BEFORE calling this tool, and pass it as workspace — do not ask the user to spell it out if it already matches one of their workspaces.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMemory UUID.
tagsNoTags attached to the memory.
sourceNoProvenance of this item (advisory, never used for auth): github, notion, workforce:<slug>, or manual. Use it to judge how much to trust the content.
contentYesFull memory text.
messageYesHuman-readable detail (same as content text).
collectionNoCollection slug, or empty string if uncategorized.
created_atNoISO 8601 creation timestamp.
importanceNoRelevance weight from 0 to 1.
memory_typeYesCategory of the memory.
resolved_workspaceNoThe workspace this call actually operated on (defense against writing to the wrong team by typo or name collision). id=null means Personal.
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the tool is safe. The description adds valuable behavioral context: workspace confirmation behavior (optionally pass workspace to confirm membership, errors if not) and echoed resolved_workspace. This goes beyond annotations without contradiction.

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?

The description is efficiently structured: first sentence states purpose, then usage scenario, return fields, UUID source, and workspace behavior. Every sentence adds value with no redundancy.

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?

Given the tool's low complexity (2 params, one required) and existence of output schema, the description covers all necessary context: what it returns, how to use parameters, and when to invoke. No gaps remain.

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% with descriptions for both parameters. The tool description adds extra meaning: explains how to get memory_id (from prior list/recall) and details workspace parameter behavior (confirmation vs error). This supplements the schema effectively.

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?

The description clearly states 'Retrieve the full content and metadata of one memory by its UUID' using a specific verb and resource. It distinguishes from sibling tools like list_memories (which returns truncated previews) and recall.

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?

It explicitly says 'Use after list_memories or recall returned a truncated preview and you need the complete text', providing clear when-to-use context. It also implies when not to use (if preview suffices) and guides on obtaining the UUID.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gpitrella/memxus-remote-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server