Skip to main content
Glama
Pseudogiant-xr

PseudoLife-MCP

Official
by Pseudogiant-xr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

memory_consolidate

Destructive

Replace a cluster of near-duplicate memories with one canonical note while keeping the replaced entries as history.

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

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoLabels for the new note.
sourceNoSource tag for the new note.
new_textYesThe canonical note that replaces them.
replacesNoUnique exact stored texts; omit with entry_ids.
entry_idsNoPositive IDs in this bank; prefer over replaces.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.16.0
    • 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"
+]
  2. Changed4 schema fields changedv0.15.0
    • 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."
  3. First observedv0.11.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds real behavior beyond the annotations: all-or-nothing atomicity ('All targets must resolve before any changes'), the exact failure modes that suppress mutation ('Missing, retired or ambiguous'), and the post-condition that 'selected entries remain as history after replacement.' These are the facts an agent needs before a destructive call and none are in the hints.

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-loads the action, then constraint, then failure behavior, then return shape. No sentence is filler; the return-key line is dense and useful.

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, atomic, multi-target mutation, the description covers what is replaced, how targets are selected, what happens on failure, and what history remains. The output schema exists and the description's return summary is a harmless convenience rather than a gap.

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 selector-mode semantics on top: exactly one of 'replaces'/'entry_ids' must be used and there is no similarity fallback, which is stronger than the schema's 'omit with entry_ids.'

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') with the outcome ('one canonical note'), so the agent knows exactly what it does. It does not differentiate from the sibling memory_supersede, which arguably overlaps, leaving the agent to infer the boundary.

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 rules: 'Use exactly one selector mode; there is no similarity fallback,' plus the failure path ('search again and resubmit IDs'). It stops short of naming the sibling tool an agent should use instead when it does not already have a resolved cluster.

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

Deploy Server

Other Tools