Skip to main content
Glama
zensation-ai

ZenBrain

Official
by zensation-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Forget a memory

zenbrain_forget
DestructiveIdempotent

Permanently delete a memory by its id and layer, plus linked consolidated copies, when a user asks to forget something or a stored memory is wrong.

Instructions

Permanently delete a memory, addressed by the id and layer that zenbrain_recall returned for it, together with what consolidation linked to it; this cannot be undone. Forgetting an episode also deletes the fact zenbrain_consolidate made from it; forgetting such a fact also deletes every episode consolidated into it; both also delete the working-memory copies of that content. Forgetting a working-memory result deletes only that copy. alsoForgotten lists everything deleted besides the memory itself. A memory stored on its own and never consolidated keeps its long-term entry. Use it when the user asks to forget something or a stored memory is wrong; to correct a memory, forget it and store the corrected version with zenbrain_store. An id the layer does not hold is reported as not forgotten, not as an error.

Input Schema

NameRequiredDescriptionDefault
idYesThe id of one result from zenbrain_recall.
layerYesThe layer of that same result, exactly as zenbrain_recall reported it.

Output Schema

NameRequiredDescriptionDefault
idYes
layerYes
forgottenYesTrue if the memory was deleted, false if the layer held none with that id.
alsoForgottenYesMemories deleted with it: what consolidation linked to it (derived from it, or it from), and working-memory copies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • addedOutput schema / properties / alsoForgotten
      Added value: +{
+  "description": "Memories deleted with it: what consolidation linked to it (derived from it, or it from), and working-memory copies.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "layer": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "layer"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "forgotten",
-  "id",
-  "layer"
-]New value: +[
+  "forgotten",
+  "id",
+  "layer",
+  "alsoForgotten"
+]
  2. Addedv0.5.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, but the description goes well beyond them: it describes the cascade in both directions (episode→fact, fact→consolidated episodes, working-memory copies), the survival rule for unconsolidated memories, the alsoForgotten field, and the non-error handling of a layer/id mismatch. That is exactly the behavior an agent needs before invoking an irreversible delete.

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?

Front-loaded with the destructive action, and the cascade, exception-handling, and usage sentences each add distinct information. It is dense and somewhat run-on (semicolon-chained cascade rules), but no sentence is filler.

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?

Output schema exists so return values need no explanation, yet the description still flags the alsoForgotten field, covers irreversible cascade semantics, distinguishes the working-memory-only case, and routes users to the store-corrected-version workflow. Nothing an agent needs to call this safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are already documented as coming from a zenbrain_recall result, so the schema carries the load. The description reinforces the coupling ('the id and layer that zenbrain_recall returned for it') but adds no format, syntax, or edge-case detail beyond what is already structured.

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?

Specific verb+resource ('Permanently delete a memory') with scope stated up front, and it names the sibling that supplies its inputs (zenbrain_recall). An agent can distinguish this from zenbrain_store and zenbrain_consolidate without opening another 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?

Explicit when-to-use ('when the user asks to forget something or a stored memory is wrong') plus the correction workflow ('forget it and store the corrected version with zenbrain_store'). It also names the counter-case: an id the layer does not hold is reported as not forgotten rather than an error.

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