open-memex

Overview Schema Source Related Servers Discussions Admin

memory_supersede

Replace an outdated saved memory with a corrected version while keeping the old one as history, so retrieval returns the new content instead of duplicates.

Instructions

Replace an existing memory with a newer version. The old memory is kept as history (status: superseded) and retrieval returns the new one. Use when a saved fact becomes outdated and should be replaced rather than duplicated. Only active memories can be superseded; the new memory inherits type, tags, and aliases unless you pass replacements. An unknown id is reported back as a failure; nothing is written.

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": {
      "id": "<id>",
      "content": "<content>"
    },
    "name": "memory_supersede"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	ID of the memory being replaced.
`tags`	No	Optional tags for the new memory.
`type`	No	Category of the new memory. Defaults to the old memory's type.
`alias`	No	D81: nickname the new memory defines (e.g. 香蕉计划). Omitted = inherit the old memory's alias.
`target`	No	D81: what `alias` refers to (e.g. 支付系统重构项目). Omitted = inherit.
`aliases`	No	Optional: alternate phrasings of this fact — synonyms, another way a question might be worded, equivalents in the user's other language (e.g. 节假日 for 'public holidays'). They are indexed with the memory so differently-worded questions still match. Always on. Send at most 4; extras and blanks are dropped silently, never an error.
`content`	Yes	The new, corrected content.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.8.2Oct 30, 2026

addedInput schema / properties / alias

Added value: +{
+  "description": "D81: nickname the new memory defines (e.g. 香蕉计划). Omitted = inherit the old memory's alias.",
+  "type": "string"
+}

changedInput schema / properties / aliases / description

Previous value: -"Optional: alternate phrasings of this fact — synonyms, another way a question might be worded, equivalents in the user's other language (e.g. 节假日 for 'public holidays'). They are indexed with the memory so differently-worded questions still match. Only used when the install has capture aliases enabled (init default). Send at most 4; extras and blanks are dropped silently, never an error."New value: +"Optional: alternate phrasings of this fact — synonyms, another way a question might be worded, equivalents in the user's other language (e.g. 节假日 for 'public holidays'). They are indexed with the memory so differently-worded questions still match. Always on. Send at most 4; extras and blanks are dropped silently, never an error."

addedInput schema / properties / target

Added value: +{
+  "description": "D81: what `alias` refers to (e.g. 支付系统重构项目). Omitted = inherit.",
+  "type": "string"
+}

First observedOct 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that the old memory is retained as history with status superseded, that retrieval returns the new one, that inheritance of type/tags/aliases happens by default, and that an unknown id fails without writing anything. This is consistent with destructiveHint=false and gives the agent real consequences to reason about.

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?

Five short sentences, front-loaded with the action and its contrast, then the precondition, then inheritance, then the failure mode. No sentence is redundant and nothing is buried.

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?

With no output schema, the description still covers the return-relevant behavior (retrieval returns the new one; unknown id surfaces as a failure with nothing written) and covers the inheritance defaults. For a 7-param mutation tool this is complete enough to call correctly.

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%, so the baseline is 3, but the description adds genuine semantics the schema only hints at: the new memory inherits type, tags, and aliases unless replacements are passed. That inheritance rule is the main thing an agent needs to decide which optional params to omit.

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 and resource ("Replace an existing memory with a newer version") and immediately contrasts it with the duplication path a sibling like memory_add would take. An agent can distinguish this from memory_add without opening either schema.

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?

Gives an explicit trigger ("Use when a saved fact becomes outdated and should be replaced rather than duplicated") plus a precondition ("Only active memories can be superseded"). It does not name memory_add directly as the alternative, which keeps it just short of a 5.

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

Deploy Server