Skip to main content
Glama
Pseudogiant-xr

PseudoLife-MCP

Official
by Pseudogiant-xr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

memory_forget

Destructive

Delete or retire entries from memory stores: hard-delete memories/facts or retire world/lesson slots with an audit trail, selected by scope.

Instructions

Forget from one memory store. memory hard-deletes entries (junk/test cleanup), retiring their digests and facts/edges left unsupported; fact hard-deletes (no audit trail); world and lesson RETIRE the slot with an audit row, undone by memory_graph_review( action="restore_slot"). For "now wrong, keep history" use memory_fact_set (facts) or memory_supersede (memories) instead.

scope="memory" needs at least one of text/substring/ source/episode/tag; several NARROW the match (AND, like memory_search): text + source is one entry, not the whole source. Over memory.delete_confirm_threshold (20) matches it refuses with would_delete until confirm_bulk=True. The other scopes need entity.

Returns: {deleted_count | removed, ...}; {error} on bad input.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNomemory scope: entries carrying this tag.
textNomemory scope: entries with exactly this text.
scopeYesWhich store to delete from.
entityNofact/world scope: the slot's subject. lesson scope: the task.
sourceNomemory scope: entries with this source tag.
episodeNomemory scope: entries stamped with this episode id.
attributeNofact/world scope: one slot's attribute; omit to purge the whole entity. lesson scope: the aspect.
substringNomemory scope: entries whose text contains this.
confirm_bulkNomemory scope: allow over memory.delete_confirm_threshold (20) matches; else refused, reporting would_delete.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.16.0
    • addedInput schema / properties / confirm_bulk
      Added value: +{
+  "default": false,
+  "description": "memory scope: allow over memory.delete_confirm_threshold (20) matches; else refused, reporting would_delete.",
+  "title": "Confirm Bulk",
+  "type": "boolean"
+}
    • changedInput schema / properties / episode / description
      Previous value: -"memory scope: delete entries stamped with this episode id."New value: +"memory scope: entries stamped with this episode id."
    • changedInput schema / properties / source / description
      Previous value: -"memory scope: delete entries with this source tag."New value: +"memory scope: entries with this source tag."
    • changedInput schema / properties / substring / description
      Previous value: -"memory scope: delete entries whose text contains this."New value: +"memory scope: entries whose text contains this."
    • changedInput schema / properties / tag / description
      Previous value: -"memory scope: delete entries carrying this tag."New value: +"memory scope: entries carrying this tag."
    • changedInput schema / properties / text / description
      Previous value: -"memory scope: delete entries whose text matches this exactly."New value: +"memory scope: entries with exactly this text."
  2. Changed8 schema fields changedv0.15.0
    • addedInput schema / properties / attribute / description
      Added value: +"fact/world scope: one slot's attribute; omit to purge the whole entity. lesson scope: the aspect."
    • addedInput schema / properties / entity / description
      Added value: +"fact/world scope: the slot's subject. lesson scope: the task."
    • addedInput schema / properties / episode / description
      Added value: +"memory scope: delete entries stamped with this episode id."
    • addedInput schema / properties / scope / description
      Added value: +"Which store to delete from."
    • addedInput schema / properties / source / description
      Added value: +"memory scope: delete entries with this source tag."
    • addedInput schema / properties / substring / description
      Added value: +"memory scope: delete entries whose text contains this."
    • addedInput schema / properties / tag / description
      Added value: +"memory scope: delete entries carrying this tag."
    • addedInput schema / properties / text / description
      Added value: +"memory scope: delete entries whose text matches this exactly."
  3. First observedv0.11.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds material context beyond them: memory/fact are hard-deletes with no audit trail (retiring digests and orphaning facts/edges), while world/lesson retire with an audit row undoable via memory_graph_review(restore_slot), and the bulk-confirm refusal path at 20 matches. This is exactly the behavioral depth the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is front-loaded with the per-scope behavior, then parameter constraints, then the return shape. It is information-dense but a single sentence spans hard-delete vs retire plus the restore path, which slightly crowds the structure. Nothing is wasted.

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 9-parameter destructive tool with an output schema, the description covers the per-scope effects, required-parameter alternatives, destroy-vs-retire semantics, the bulk-confirm guard, and the escape hatches (memory_fact_set, memory_supersede, restore_slot). An agent has everything needed to call it 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. The description adds real value on top by stating that scope=memory needs at least one of text/substring/source/episode/tag, that several narrow via AND rather than widening, and that the other scopes require entity – conditions the per-property schema descriptions don't capture.

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 gives a specific verb ('Forget' / hard-delete / retire) and resource (entries across four named scopes), and names the sibling tools (memory_fact_set, memory_supersede, memory_graph_review) with which it could be confused. It distinctly differentiates itself by scope behavior, which no other sibling does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states which alternative to use for the 'now wrong, keep history' case – memory_fact_set for facts and memory_supersede for memories – and carves out when hard-delete is appropriate (junk/test cleanup) versus when retiring is appropriate. When-not guidance is explicit.

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