XMemo

Update XMemo memory

update_memory

Destructive

Updates the content, location, or type of a specific saved memory when the user asks to correct, revise, move, or reclassify it. An exact reference identifies the record.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No	A simple user-facing category or path for this memory, such as preferences, projects/xmemo, or personal/travel.
`scope`	No	Optional scope that narrows memory access; leave blank for the token default.
`bucket`	No	Memory bucket or namespace to read from or write to; use % only for tools that support wildcard reads.
`status`	No	Memory status filter or update value, such as active, archived, deleted, or %.
`content`	No	Text body to save, such as a memory, TODO/action item, event note, or state summary.
`team_id`	No	Optional team/workspace identifier for team-scoped memory access.
`memory_id`	Yes	Exact XMemo memory reference shown by search or recall.
`confidence`	No	Confidence score for the saved or updated memory, from 0.0 to 1.0.
`expires_at`	No	Optional ISO 8601 expiration timestamp for the memory.
`importance`	No	Importance score for the saved or updated memory, from 0.0 to 1.0.
`memory_type`	No	Memory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %.
`semantic_key`	No	Optional stable key for one evolving fact: changed body upserts it, the same normalized body is idempotent; metadata_json.semantic_key_mode='merge_metadata' preserves the body while merging metadata.
`metadata_json`	No	Optional JSON object string with extra metadata for the operation.	{}
`merge_metadata`	No	Whether to merge new metadata with existing metadata instead of replacing it.
`provenance_json`	No	Optional JSON object string describing memory source, evidence, or attribution.	{}
`detect_conflicts`	No	Whether to detect possible conflicts with existing memories during an update.
`merge_provenance`	No	Whether to merge new provenance with existing provenance instead of replacing it.
`supersession_reason`	No	Reason the updated memory supersedes older content.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedSep 11, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / bucket

Added value: +{
+  "default": "",
+  "description": "Memory bucket or namespace to read from or write to; use % only for tools that support wildcard reads.",
+  "title": "Bucket",
+  "type": "string"
+}

addedInput schema / properties / confidence

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Confidence score for the saved or updated memory, from 0.0 to 1.0.",
+  "title": "Confidence"
+}

addedInput schema / properties / detect_conflicts

Added value: +{
+  "default": true,
+  "description": "Whether to detect possible conflicts with existing memories during an update.",
+  "title": "Detect Conflicts",
+  "type": "boolean"
+}

addedInput schema / properties / expires_at

Added value: +{
+  "default": "",
+  "description": "Optional ISO 8601 expiration timestamp for the memory.",
+  "title": "Expires At",
+  "type": "string"
+}

addedInput schema / properties / importance

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Importance score for the saved or updated memory, from 0.0 to 1.0.",
+  "title": "Importance"
+}

changedInput schema / properties / memory_type / description

Previous value: -"Optional memory type/category for user-facing updates, such as semantic, episodic, or procedural."New value: +"Memory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %."

addedInput schema / properties / merge_metadata

Added value: +{
+  "default": true,
+  "description": "Whether to merge new metadata with existing metadata instead of replacing it.",
+  "title": "Merge Metadata",
+  "type": "boolean"
+}

addedInput schema / properties / merge_provenance

Added value: +{
+  "default": true,
+  "description": "Whether to merge new provenance with existing provenance instead of replacing it.",
+  "title": "Merge Provenance",
+  "type": "boolean"
+}

addedInput schema / properties / metadata_json

Added value: +{
+  "default": "{}",
+  "description": "Optional JSON object string with extra metadata for the operation.",
+  "title": "Metadata Json",
+  "type": "string"
+}

addedInput schema / properties / provenance_json

Added value: +{
+  "default": "{}",
+  "description": "Optional JSON object string describing memory source, evidence, or attribution.",
+  "title": "Provenance Json",
+  "type": "string"
+}

addedInput schema / properties / scope

Added value: +{
+  "default": "",
+  "description": "Optional scope that narrows memory access; leave blank for the token default.",
+  "title": "Scope",
+  "type": "string"
+}

addedInput schema / properties / semantic_key

Added value: +{
+  "default": "",
+  "description": "Optional stable key for one evolving fact: changed body upserts it, the same normalized body is idempotent; metadata_json.semantic_key_mode='merge_metadata' preserves the body while merging metadata.",
+  "title": "Semantic Key",
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "default": "",
+  "description": "Memory status filter or update value, such as active, archived, deleted, or %.",
+  "title": "Status",
+  "type": "string"
+}

addedInput schema / properties / supersession_reason

Added value: +{
+  "default": "",
+  "description": "Reason the updated memory supersedes older content.",
+  "title": "Supersession Reason",
+  "type": "string"
+}

addedInput schema / properties / team_id

Added value: +{
+  "default": "",
+  "description": "Optional team/workspace identifier for team-scoped memory access.",
+  "title": "Team Id",
+  "type": "string"
+}

Changed16 schema fields changedJul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / bucket

Removed value: -{
-  "default": "",
-  "description": "Memory bucket or namespace to read from or write to; use % only for tools that support wildcard reads.",
-  "title": "Bucket",
-  "type": "string"
-}

removedInput schema / properties / confidence

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Confidence score for the saved or updated memory, from 0.0 to 1.0.",
-  "title": "Confidence"
-}

removedInput schema / properties / detect_conflicts

Removed value: -{
-  "default": true,
-  "description": "Whether to detect possible conflicts with existing memories during an update.",
-  "title": "Detect Conflicts",
-  "type": "boolean"
-}

removedInput schema / properties / expires_at

Removed value: -{
-  "default": "",
-  "description": "Optional ISO 8601 expiration timestamp for the memory.",
-  "title": "Expires At",
-  "type": "string"
-}

removedInput schema / properties / importance

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Importance score for the saved or updated memory, from 0.0 to 1.0.",
-  "title": "Importance"
-}

changedInput schema / properties / memory_type / description

Previous value: -"Memory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %."New value: +"Optional memory type/category for user-facing updates, such as semantic, episodic, or procedural."

removedInput schema / properties / merge_metadata

Removed value: -{
-  "default": true,
-  "description": "Whether to merge new metadata with existing metadata instead of replacing it.",
-  "title": "Merge Metadata",
-  "type": "boolean"
-}

removedInput schema / properties / merge_provenance

Removed value: -{
-  "default": true,
-  "description": "Whether to merge new provenance with existing provenance instead of replacing it.",
-  "title": "Merge Provenance",
-  "type": "boolean"
-}

removedInput schema / properties / metadata_json

Removed value: -{
-  "default": "{}",
-  "description": "Optional JSON object string with extra metadata for the operation.",
-  "title": "Metadata Json",
-  "type": "string"
-}

removedInput schema / properties / provenance_json

Removed value: -{
-  "default": "{}",
-  "description": "Optional JSON object string describing memory source, evidence, or attribution.",
-  "title": "Provenance Json",
-  "type": "string"
-}

removedInput schema / properties / scope

Removed value: -{
-  "default": "",
-  "description": "Optional scope that narrows memory access; leave blank for the token default.",
-  "title": "Scope",
-  "type": "string"
-}

removedInput schema / properties / semantic_key

Removed value: -{
-  "default": "",
-  "description": "Optional stable semantic key used to identify or upsert a memory concept.",
-  "title": "Semantic Key",
-  "type": "string"
-}

removedInput schema / properties / status

Removed value: -{
-  "default": "",
-  "description": "Memory status filter or update value, such as active, archived, deleted, or %.",
-  "title": "Status",
-  "type": "string"
-}

removedInput schema / properties / supersession_reason

Removed value: -{
-  "default": "",
-  "description": "Reason the updated memory supersedes older content.",
-  "title": "Supersession Reason",
-  "type": "string"
-}

removedInput schema / properties / team_id

Removed value: -{
-  "default": "",
-  "description": "Optional team/workspace identifier for team-scoped memory access.",
-  "title": "Team Id",
-  "type": "string"
-}

First observedJun 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the agent knows this is a write/update operation. The description adds valuable behavioral context by specifying that updates can affect 'content, location, or type' and that an 'exact reference' (memory_id) is required to identify the record. This goes beyond raw annotations without contradicting them.

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 two sentences, front-loads the core action, and every phrase earns its place. It avoids fluff, restating the title, or repeating schema details. The structure is efficient and immediately informative.

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 mutation tool with a rich schema and output schema, the description is sufficiently complete to guide usage. It conveys the essential context (when to use, what it updates) and the need for an exact reference. It does not describe return values, but the presence of an output schema makes that unnecessary. A minor omission is explicit mention of potential side effects like conflict detection or supersession, but these are evident from the parameter names.

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?

The input schema provides 100% coverage with descriptions for all 18 parameters. The description does not add parameter-specific details beyond what the schema already offers, but it does map 'content', 'location', and 'type' to likely parameters (content, path, memory_type). Since the schema is thorough, a baseline of 3 is appropriate; the description's mention adds only marginal value.

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 a specific verb ('updates') and the target resource ('a specific saved memory'), and distinguishes this tool from siblings like 'remember' (create), 'forget' (delete), and 'read_memory' by specifying it handles corrections, revisions, moves, or reclassifications. This unambiguously identifies the tool's unique role.

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?

Explicitly states when to use the tool: 'when the user asks to correct, revise, move, or reclassify it.' This provides clear contextual triggers. However, it does not explicitly mention when not to use it or name alternatives (e.g., use 'remember' for entirely new memories), so it stops short of a full 5.

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

All XMemo tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.