Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Revise a neuron

crbro_revise
Idempotent

Retire outdated or false facts and entries from recall without deleting them; keep them on disk and reactivate later when a replacement exists.

Instructions

Write: change what a neuron says without deleting anything. Stage 2 of the lifecycle: something stopped being true, or was never true, and nothing replaces it → crbro_revise (kept in the file, gone from recall, reversible with status active). If a replacement exists, crbro_learn with supersedes does both; for what must not exist on disk use crbro_forget. facts retires facts by id or exact text; entries retires decisions, patterns, errors and debts by exact text; status active reactivates either (local only on a shared neuron: the next sync re-applies the retirement, shared_warning says so). summary, domain, tags and name edit metadata in the same call (tags replaces the whole list; the id never changes). Anything in unmatched is STILL LIVE — fix and re-run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoRename the neuron. Its id, file, synapses and shared state stay the same.
noteNoWhy. Stored as revision_note on facts and entry_status.note on entries. The next reader will wonder.
tagsNoReplace the WHOLE tag list (trimmed, deduplicated). On protocol neurons re-send the priority: and source: tags or they are gone.
factsNoFacts to move to `status`: their ids (from crbro_recall) or exact text (trimmed, case-insensitive). For superseded/retracted only active facts match; for active only retired ones do.
domainNoReplace the neuron domain unconditionally, e.g. "proyectos-web".
neuronYesNeuron id or name holding what to revise, e.g. "project_octochat".
statusNosuperseded = a newer truth exists (default); retracted = it was never true; active = reactivate a retired fact or entry. Reactivation is local: on a shared neuron the next sync re-applies the retirement (the response carries shared_warning).
entriesNoExact texts of decisions, patterns, errors or debts to move to `status`. Retired entries stay in the file (entry_status) but leave recall like a superseded fact.
summaryNoReplace the neuron summary. Credentials are redacted and listed in redacted.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv2.0.0
    • addedInput schema / properties / domain
      Added value: +{
+  "description": "Replace the neuron domain unconditionally, e.g. \"proyectos-web\".",
+  "type": "string"
+}
    • addedInput schema / properties / entries
      Added value: +{
+  "description": "Exact texts of decisions, patterns, errors or debts to move to `status`. Retired entries stay in the file (entry_status) but leave recall like a superseded fact.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / facts / description
      Previous value: -"Facts to retire: their ids (from crbro_recall) or exact text (trimmed, case-insensitive). Already-retired facts never match."New value: +"Facts to move to `status`: their ids (from crbro_recall) or exact text (trimmed, case-insensitive). For superseded/retracted only active facts match; for active only retired ones do."
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Rename the neuron. Its id, file, synapses and shared state stay the same.",
+  "type": "string"
+}
    • changedInput schema / properties / neuron / description
      Previous value: -"Neuron id or name holding the facts, e.g. \"project_octochat\"."New value: +"Neuron id or name holding what to revise, e.g. \"project_octochat\"."
    • changedInput schema / properties / note / description
      Previous value: -"Why it stopped being true. The next reader will wonder."New value: +"Why. Stored as revision_note on facts and entry_status.note on entries. The next reader will wonder."
    • changedInput schema / properties / status / description
      Previous value: -"superseded = there is a newer truth (default); retracted = it was never true."New value: +"superseded = a newer truth exists (default); retracted = it was never true; active = reactivate a retired fact or entry. Reactivation is local: on a shared neuron the next sync re-applies the retirement (the response carries shared_warning)."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "superseded",
-  "retracted"
-]New value: +[
+  "superseded",
+  "retracted",
+  "active"
+]
    • addedInput schema / properties / summary
      Added value: +{
+  "description": "Replace the neuron summary. Credentials are redacted and listed in redacted.",
+  "type": "string"
+}
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Replace the WHOLE tag list (trimmed, deduplicated). On protocol neurons re-send the priority: and source: tags or they are gone.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "neuron",
-  "facts"
-]New value: +[
+  "neuron"
+]
  2. Addedv1.14.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint false, destructiveHint false, and idempotentHint true, and the description adds meaningful context beyond those: 'without deleting anything,' 'kept in the file, gone from recall, reversible with status active,' the local-only reactivation caveat on shared neurons, 'tags replaces the whole list,' and 'Anything in unmatched is STILL LIVE — fix and re-run.' This fully discloses side effects and non-destructive behavior.

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

Conciseness5/5

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

The description is dense but every clause earns its place; it front-loads the one-line purpose and then packs lifecycle context, sibling differentiation, parameter behavior, metadata editing, and warnings into a compact form. There is no filler or repetition.

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 complex tool with 9 parameters and no output schema, the description covers the lifecycle stage, alternatives, matching semantics, status meanings, shared-neuron caveats, metadata edits, and the unmatched-live warning. Even the response's shared_warning is anticipated. Nothing essential for selecting or invoking the tool correctly is missing.

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%, so the baseline is 3, but the description meaningfully enriches the parameters: it explains facts vs entries matching by id or exact text, default status 'superseded', active-only vs retired-only matching, the local reactivation limitation, and that tags replaces the whole list. This goes well beyond the schema's per-field descriptions.

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 opens with a concrete verb and resource: 'Write: change what a neuron says without deleting anything,' followed by its lifecycle stage. It clearly distinguishes crbro_revise from siblings by naming crbro_learn with supersedes and crbro_forget as alternatives, so an agent can tell them apart.

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 gives explicit when-to-use guidance: 'something stopped being true, or was never true, and nothing replaces it → crbro_revise.' It also gives when-not-to-use and alternatives: 'If a replacement exists, crbro_learn with supersedes does both; for what must not exist on disk use crbro_forget.' This is exactly the routing information an agent needs.

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