Skip to main content
Glama

Update XMemo memory

update_memory

Update an existing memory's content, location, or type. Use to correct, revise, move, or reclassify a saved memory.

Instructions

Update the content, location, or type of an existing memory. Call this only when the user explicitly asks to correct, revise, move, or reclassify a specific saved memory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoA simple user-facing category or path for this memory, such as preferences, projects/xmemo, or personal/travel.
scopeNoOptional scope that narrows memory access; leave blank for the token default.
bucketNoMemory bucket or namespace to read from or write to; use % only for tools that support wildcard reads.
statusNoMemory status filter or update value, such as active, archived, deleted, or %.
contentNoText body to save, such as a memory, TODO/action item, event note, or state summary.
team_idNoOptional team/workspace identifier for team-scoped memory access.
memory_idYesExact XMemo memory reference shown by search or recall.
confidenceNoConfidence score for the saved or updated memory, from 0.0 to 1.0.
expires_atNoOptional ISO 8601 expiration timestamp for the memory.
importanceNoImportance score for the saved or updated memory, from 0.0 to 1.0.
memory_typeNoMemory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %.
semantic_keyNoOptional stable semantic key used to identify or upsert a memory concept.
metadata_jsonNoOptional JSON object string with extra metadata for the operation.{}
merge_metadataNoWhether to merge new metadata with existing metadata instead of replacing it.
provenance_jsonNoOptional JSON object string describing memory source, evidence, or attribution.{}
detect_conflictsNoWhether to detect possible conflicts with existing memories during an update.
merge_provenanceNoWhether to merge new provenance with existing provenance instead of replacing it.
supersession_reasonNoReason the updated memory supersedes older content.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that the tool modifies existing memories but doesn't disclose side effects, reversibility, or permission requirements. With annotations bearing partial burden, the description adds moderate value.

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?

Two sentences, front-loaded with action, no wasted words. Efficient and clear.

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?

Despite 18 parameters, the description is sufficient for an update operation with an existing output schema. It covers core purpose and usage context, though it could mention return value or more behavioral details.

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 covers 100% of parameters with individual descriptions. The description mentions 'content, location, or type' which maps to schema fields but does not add meaning beyond what is already in the schema. 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?

Description explicitly states 'Update the content, location, or type of an existing memory.' It uses a specific verb ('update') and resource ('existing memory'), and distinguishes from sibling tools like 'remember' (create) and 'forget' (delete).

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?

Description clearly says 'Call this only when the user explicitly asks to correct, revise, move, or reclassify a specific saved memory.' This provides explicit context for use, though it doesn't list alternative tools for other scenarios.

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/yonro/memory-os-cli'

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