PseudoLife-MCP

Official

Overview Schema Source Related Servers Discussions Admin

memory_forget

Destructive

Delete or retire wrong or obsolete memories, facts, world knowledge, or lessons by scope; confirm bulk removals to prevent accidental mass deletion.

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

Name	Required	Description
`tag`	No	memory scope: entries carrying this tag.
`text`	No	memory scope: entries with exactly this text.
`scope`	Yes	Which store to delete from.
`entity`	No	fact/world scope: the slot's subject. lesson scope: the task.
`source`	No	memory scope: entries with this source tag.
`episode`	No	memory scope: entries stamped with this episode id.
`attribute`	No	fact/world scope: one slot's attribute; omit to purge the whole entity. lesson scope: the aspect.
`substring`	No	memory scope: entries whose text contains this.
`confirm_bulk`	No	memory scope: allow over memory.delete_confirm_threshold (20) matches; else refused, reporting would_delete.

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
```

Changed6 schema fields changedv0.16.0Oct 3, 2026

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."

Changed8 schema fields changedv0.15.0Sep 3, 2026

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."

First observedv0.11.0Jul 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the destructiveHint annotation by disclosing which scopes hard-delete with no audit trail (fact) versus retire with an audit row (world/lesson), the confirm_bulk threshold of 20, and the would_delete refusal shape. These are exactly the behavioral facts an agent needs before a destructive call.

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?

Dense but front-loaded: scope behaviors first, then alternatives, then filter rules, then the bulk-refusal guard. Every clause carries information, though the backtick-heavy formatting and run-on density cost it a point.

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?

Given 9 parameters, an output schema, and destructive annotations, the description covers the required scope-dependent rules, the bulk-confirmation guard, and the undo path. Nothing material to correct invocation 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, but the description adds cross-parameter semantics the schema cannot express: scope="memory" needs at least one filter, several filters NARROW the match (AND), and non-memory scopes require entity. This mapping of filters to scopes is genuinely additive.

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 (forget/delete/retire) and resource (memory store) and enumerates the four scopes with their distinct behaviors. An agent can distinguish this from siblings like memory_supersede or memory_fact_set without opening a schema.

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?

Explicitly routes the agent: 'For now wrong, keep history use memory_fact_set (facts) or memory_supersede (memories) instead,' and names memory_graph_review(action="restore_slot") as the undo path. When-to-use and when-to-use-something-else are both stated.

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