Skip to main content
Glama

memxus

by com.memxus

Get memory

get_memory
Read-onlyIdempotent

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. Call list_collections when unsure of the exact workspace name.

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.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds valuable context: return fields, workspace echo and confirmation behavior, and error cases.

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?

The description is well-structured with front-loaded purpose and subsequent details. It is thorough but not excessively long; could slightly trim workspace explanation.

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 output schema exists and is summarized in description, all necessary info is present. Parameters fully covered, return values listed, workspace behavior explained.

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 description coverage is 100% so baseline 3. Description adds guidance on UUID source and workspace parameter behavior, enhancing semantic understanding.

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 the verb 'Retrieve' and resource 'the full content and metadata of one memory by its UUID'. It distinguishes from sibling tools list_memories and recall by specifying when to use it (after a truncated preview).

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 states when to use: 'Use after list_memories or recall returned a truncated preview and you need the complete text.' Also gives source for UUID and optional workspace usage.

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

All memxus toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: forget deletes, remember saves, update modifies, recall searches, list_memories lists, get_memory retrieves full details, get_context builds a context block, list_collections lists folders, memory_stats shows counts. There is no functional overlap that would confuse an agent.

Naming Consistency3/5

Names mix conventions: forget, recall, remember, update are single verbs; get_context, get_memory, list_collections, list_memories follow verb_noun; memory_stats is noun_noun. This inconsistency can make it harder for an agent to predict tool names.

Tool Count5/5

With 9 tools, the server is well-scoped for a memory management system. Each tool addresses a core operation (CRUD, search, stats, context building) without unnecessary redundancy. The count is appropriate for the domain.

Completeness4/5

The surface covers create (remember), read (list_memories, get_memory, recall, get_context), update (update), delete (forget), plus metadata tools (list_collections, memory_stats). Missing explicit filtering by tags or bulk operations, but these are minor gaps given the semantic search capability.

Resources