PseudoLife-MCP

Official

Overview Schema Source Related Servers Discussions Admin

memory_consolidate

Destructive

Merge duplicate memories into one canonical note using exact texts or entry IDs; all targets must resolve before any changes.

Instructions

Replace a cluster of near-duplicate memories with one canonical note. Use exactly one selector mode; there is no similarity fallback. All targets must resolve before any changes. Missing, retired or ambiguous targets cause no mutation; search again and resubmit IDs. Selected entries remain as history after replacement.

Returns: {superseded_count, superseded_texts, superseded_ids, new_memory_stored}.

Input Schema

Name	Required	Description
`tags`	No	Labels for the new note.
`source`	No	Source tag for the new note.
`new_text`	Yes	The canonical note that replaces them.
`replaces`	No	Unique exact stored texts; omit with entry_ids.
`entry_ids`	No	Positive IDs in this bank; prefer over replaces.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.18.1Oct 14, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed7 schema fields changedv0.16.0Oct 3, 2026

addedInput schema / properties / entry_ids

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Positive IDs in this bank; prefer over replaces.",
+  "title": "Entry Ids"
+}

addedInput schema / properties / replaces / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / replaces / default
```
Added value: +null
```

changedInput schema / properties / replaces / description

Previous value: -"The memories being folded in; each is matched by exact text or close paraphrase."New value: +"Unique exact stored texts; omit with entry_ids."

removedInput schema / properties / replaces / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / replaces / type
```
Removed value: -"array"
```

changedInput schema / required

Previous value: -[
-  "replaces",
-  "new_text"
-]New value: +[
+  "new_text"
+]

Changed4 schema fields changedv0.15.0Sep 3, 2026
- addedInput schema / properties / new_text / description
```
Added value: +"The canonical note that replaces them."
```
- addedInput schema / properties / replaces / description
```
Added value: +"The memories being folded in; each is matched by exact text or close paraphrase."
```
- addedInput schema / properties / source / description
```
Added value: +"Source tag for the new note."
```
- addedInput schema / properties / tags / description
```
Added value: +"Labels for the new note."
```
First observedv0.11.0Jul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds real value beyond them: pre-flight atomicity (all targets resolve or nothing mutates) and the fact that superseded entries are retained as history rather than deleted. It doesn't cover auth/permission needs, but the mutation semantics are well disclosed.

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?

Front-loaded purpose sentence, then compact operational rules, then the return shape. Every sentence carries distinct information and nothing is padded.

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?

For a destructive consolidation tool with full schema coverage, an output schema, and safety annotations, the description covers the remaining gaps: atomicity, selector exclusivity, history retention, and the return keys. Nothing an agent needs to invoke it correctly is missing.

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. The description adds meaning beyond the schema by stating that exactly one selector mode must be used and that there is no similarity fallback, which clarifies the replaces vs entry_ids relationship that the schema only hints at with 'prefer over replaces'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (replace) and resource (a cluster of near-duplicate memories) plus the resulting artifact (one canonical note). It implicitly separates itself from single-entry tools like memory_supersede, but never names a sibling to draw the line explicitly.

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 concrete operating guidance: use exactly one selector mode, no similarity fallback, all targets must resolve before mutation, and re-search/resubmit on missing/retired/ambiguous targets. Strong when/how context, but it does not name alternative tools (e.g., memory_supersede or memory_consolidation_candidates) or state when not to consolidate.

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