Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Forget for good

crbro_forget
DestructiveIdempotent

Delete facts, neurons, or session logs permanently after a quarantine backup. Merge neurons into another, restore the newest backup, and use dry-run confirmation for whole-neuron deletion.

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. 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. Dates show when Glama detected each change.

  1. 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"
-]
  2. Addedv1.14.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say destructiveHint=true, readOnlyHint=false, idempotentHint=true. The description massively expands on this: it states quarantine copy behavior, dry-run behavior for entire mode, stale token refusal, shared-neuron refusal, merged_into_existing behavior for restore, repeatable restore, and the security warning about credential rotation. It also discloses that textual deletion itself is irreversible after quarantine. With destructiveHint=true, the description goes well beyond what annotations provide, deeply informing an agent about consequences and safeguards.

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 description is long but dense and front-loaded with the most critical information ('Write, destructive... quarantine copy'). It is organized by mode, which makes it scannable for an agent. It loses one point because it packs a lot of secondary caveats (stale token derivation from counts, moved counts, merged_into_existing) in the schema rather than the main description, and the main description is quite long, but each sentence earns its place for a destructive multi-mode tool.

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 tool with 7 parameters, 5 modes, no output schema, and only two boolean annotations, the description covers prerequisites (unshare shared neurons), sequencing (dry run first, then confirm token), safety (quarantine, restore path), security (rotation warning), and per-mode parameter requirements. No gaps are left for the agent to guess: it knows exactly what is required, what will be refused, and what will happen on success.

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

Parameters5/5

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

Schema coverage is 100%, but the description still adds meaning beyond the schema: it explains the mode gating (one mode per call), which parameter is required for which mode, the dry-run/token semantics, the exact behavior of 'facts' with decision/pattern removal propagation, and the quarantine/repeatability semantics of restore. The parameter descriptions in the schema are rich, and the main description coordinates across them with lifecycle context, prerequisites, and failure conditions.

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?

Description opens with 'Write, destructive: remove from disk after a quarantine copy (backup returned)', clearly identifying the tool as a destructive deletion operation with a safety mechanism. It enumerates five specific modes (facts, entire, restore, merge_into, session), each with a concrete effect, and distinguishes it from the sibling crbro_revise (which keeps history for knowledge that stopped being true). This is far beyond tautology and clearly separates this destructive tool from its non-destructive siblings.

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?

The description provides explicit guidance on when to use this tool vs the alternative: 'for knowledge that merely stopped being true use crbro_revise, which keeps the history' — naming the sibling and the selection condition. It also gives concrete stages of the lifecycle ('Stage 3 of the lifecycle') and per-mode behavioral directives such as the required two-call confirm_token flow, the sharing precondition (crbro_share unshare first), and the security note that a removed credential must still be rotated. This is exceptional usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Octonove/crbro-memory'

If you have feedback or need assistance with the MCP directory API, please join our Discord server