Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Forget for good

crbro_forget
DestructiveIdempotent

Permanently remove memories, credentials, or whole neurons from disk after a quarantine copy, with restore available. Deletes facts, sessions, or merges neurons while preserving a recoverable backup.

Instructions

Write, destructive: remove from disk after a quarantine copy (backup returned). Stage 3 of the lifecycle: something must not exist on disk at all — a credential, personal data, a whole neuron → crbro_forget; for knowledge that merely stopped being true use crbro_revise, which keeps the history. One mode per call. facts: delete entries of a neuron (facts, decisions, patterns, preferences, errors, debts, the map) by id or exact text. entire: delete the whole neuron and its synapses — call it without confirm_token first: the dry run reports what would happen and returns confirm_token. Show the user, get agreement, call again with the token; a stale token is refused. restore: bring back the newest quarantine copy. merge_into: union a neuron into another, rewire synapses, delete the source. session: delete one day's log, search index included (quarantine keeps the text). entire and merge_into refuse a shared neuron — crbro_share unshare first. A removed credential must still be rotated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
factsNoMode facts: fact ids, or the exact text of a fact, decision, pattern, preference, error or debt; the exact full text of the map removes the map. Deleted for good after a quarantine copy; decision/pattern removals travel to shared spaces like errors and debts.
entireNoMode entire: delete the whole neuron and its synapses. Without confirm_token it is a dry run — { neuron_id, dry_run:true, counts, shared_in, confirm_token }. Refused (no token) while the neuron is shared: crbro_share unshare first.
neuronNoNeuron id or name the mode acts on. Required for every mode except session. restore needs the exact neuron id.
restoreNoMode restore: bring back the newest quarantine copy of `neuron` (exact id). If the neuron exists again, the copy is merged into it (merged_into_existing:true, moved counts). The quarantine file stays, so restore is repeatable.
sessionNoMode session: session id ("session_2026-09-03" or "2026-09-03") whose log is deleted after a quarantine copy. `neuron` is not needed.
merge_intoNoMode merge_into: target neuron id or name. Everything of `neuron` is unioned into it, synapses rewired, then `neuron` is deleted (quarantined first). Refused while `neuron` is shared.
confirm_tokenNoOnly with entire:true — the token from the dry run. Derived from the neuron's counts, so it goes stale (and is refused) when the neuron changed in between.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed8 schema fields changedv2.0.0
    • addedInput schema / properties / confirm_token
      Added value: +{
+  "description": "Only with entire:true — the token from the dry run. Derived from the neuron's counts, so it goes stale (and is refused) when the neuron changed in between.",
+  "type": "string"
+}
    • addedInput schema / properties / entire
      Added value: +{
+  "description": "Mode entire: delete the whole neuron and its synapses. Without confirm_token it is a dry run — { neuron_id, dry_run:true, counts, shared_in, confirm_token }. Refused (no token) while the neuron is shared: crbro_share unshare first.",
+  "type": "boolean"
+}
    • changedInput schema / properties / facts / description
      Previous value: -"Fact ids, or the exact text of a fact, decision, pattern, preference, error or debt. The exact full text of the map removes the map."New value: +"Mode facts: fact ids, or the exact text of a fact, decision, pattern, preference, error or debt; the exact full text of the map removes the map. Deleted for good after a quarantine copy; decision/pattern removals travel to shared spaces like errors and debts."
    • addedInput schema / properties / merge_into
      Added value: +{
+  "description": "Mode merge_into: target neuron id or name. Everything of `neuron` is unioned into it, synapses rewired, then `neuron` is deleted (quarantined first). Refused while `neuron` is shared.",
+  "type": "string"
+}
    • changedInput schema / properties / neuron / description
      Previous value: -"Neuron id or name holding the entries."New value: +"Neuron id or name the mode acts on. Required for every mode except session. restore needs the exact neuron id."
    • addedInput schema / properties / restore
      Added value: +{
+  "description": "Mode restore: bring back the newest quarantine copy of `neuron` (exact id). If the neuron exists again, the copy is merged into it (merged_into_existing:true, moved counts). The quarantine file stays, so restore is repeatable.",
+  "type": "boolean"
+}
    • addedInput schema / properties / session
      Added value: +{
+  "description": "Mode session: session id (\"session_2026-09-03\" or \"2026-09-03\") whose log is deleted after a quarantine copy. `neuron` is not needed.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "neuron",
-  "facts"
-]
  3. Addedv1.14.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructive/readOnly/idempotent, but the description adds substantial context they cannot: every removal is preceded by a quarantine copy, entire is a dry-run-then-confirm-token flow, stale tokens are refused, shared neurons are refused, session deletes include the search index, and restore is repeatable because the quarantine file persists. This goes well beyond the annotation set.

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-loads the destructive warning and lifecycle position before enumerating modes, and every sentence (quarantine, dry run, refusals, rotation) carries operational weight. It is dense for a long single paragraph; minor restructuring into mode bullets would aid scanning, but nothing is padding.

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 7-parameter, multi-mode destructive tool with no output schema, the description supplies the missing return-shape context (dry-run counts and token, restore's merged_into_existing) and the full safety workflow. An agent has everything needed to call it correctly and safely.

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 already 100%, so the baseline is 3, but the description adds meaning the schema does not carry: the one-mode-per-call constraint, which params apply to which mode, exact-id requirements for restore, and the token's derivation from neuron counts. It clarifies orchestration rather than merely restating field docs.

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 and resource plus the distinguishing condition: removing something from disk entirely versus revising knowledge that merely stopped being true. It names the sibling (crbro_revise) and the boundary between them, so an agent can route correctly without opening either 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?

Gives explicit when-to-use triggers (a credential, personal data, a whole neuron), names the alternative and its condition, and adds mode-level routing (facts vs entire vs restore vs merge_into vs session). It also states prerequisites: dry run before entire, crbro_share unshare before entire/merge_into, credential rotation after.

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