crbro-memory

Overview Schema Source Related Servers Discussions Admin

Learn something

crbro_learn

Store a fact, decision, pattern, preference, error, or debt on a topic into persistent memory for AI assistants, creating or updating an entry, superseding old facts and merging duplicates.

Instructions

Write: store a fact, decision, pattern, preference, error or debt on a topic; the neuron is created if missing (or pass neuron_id). Stage 1 of the lifecycle: a new truth that REPLACES an old one → crbro_learn with supersedes (one call does both); to retire with no replacement use crbro_revise; to delete from disk use crbro_forget. crbro_recall first — it may already exist. The same fact text again is not duplicated: keywords merge (or keywords_replace) and a changed confidence applies (updated_in_place); text matching a retired fact or entry is refused with skipped_retired. Decisions always append; preferences never leave this machine. Credentials are replaced with a marker and listed in redacted — crbro_secret them, record only the name. Returns neuron_id, action, superseded count, near_duplicates (stored anyway; retire the old telling), supersedes_unmatched (still live) and totals.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	Yes	error = a mistake plus its correction, in one entry. debt = a deliberate deferral: what was NOT done on purpose, its ceiling, and the revisit condition, e.g. "DEFERRED: protecting the PDFs. CEILING: anyone can download them without signing up. REVISIT WHEN: the signup flow works."
`topic`	No	Topic name, e.g. "OctoChat", "Firebase", "SEO Strategy". Required UNLESS you pass neuron_id, in which case the topic is taken from that neuron.
`domain`	No	Domain, e.g. "proyectos-web". Applied when the neuron is created; on an existing neuron it only replaces the default "general" (crbro_revise domain replaces it unconditionally).
`content`	Yes	The knowledge itself. Dense and self-contained: it is recalled without this conversation as context.
`keywords`	No	Facts only. 2-5 words a future question may use that the text does not contain: synonyms, the other language, the generic name of the product named. Indexed with the fact, never shown. The same text again with new keywords merges them.
`neuron_id`	No	Exact neuron id from crbro_recall, e.g. "project_octochat". Skips name matching entirely, and then topic is not needed.
`rationale`	No	Why the decision was taken. Stored and indexed with it; ignored for other types.
`confidence`	No	0.0-1.0, default 1.0. Facts only. On an exact-duplicate active fact the stored confidence is updated to this value (updated_in_place:true).
`supersedes`	No	Facts this one replaces: their ids or exact text. They leave recall but stay in the file. Unmatched targets are reported and stay live.
`keywords_replace`	No	When the exact fact text already exists, replace its stored keywords with `keywords` instead of merging (default false). Teammates in a shared space only ever receive the union.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.4.0Sep 13, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```

Changed3 schema fields changedv2.1.0Sep 7, 2026

changedInput schema / properties / neuron_id / description

Previous value: -"Exact neuron id from crbro_recall, e.g. \"project_octochat\". Skips name matching entirely."New value: +"Exact neuron id from crbro_recall, e.g. \"project_octochat\". Skips name matching entirely, and then topic is not needed."

changedInput schema / properties / topic / description

Previous value: -"Topic name, e.g. \"OctoChat\", \"Firebase\", \"SEO Strategy\"."New value: +"Topic name, e.g. \"OctoChat\", \"Firebase\", \"SEO Strategy\". Required UNLESS you pass neuron_id, in which case the topic is taken from that neuron."

changedInput schema / required

Previous value: -[
-  "topic",
-  "type",
-  "content"
-]New value: +[
+  "type",
+  "content"
+]

Changed3 schema fields changedv2.0.0Sep 3, 2026

changedInput schema / properties / confidence / description

Previous value: -"0.0-1.0, default 1.0. Facts only."New value: +"0.0-1.0, default 1.0. Facts only. On an exact-duplicate active fact the stored confidence is updated to this value (updated_in_place:true)."

changedInput schema / properties / domain / description

Previous value: -"Domain, e.g. \"proyectos-web\". Applied when the neuron is created; on an existing neuron it only replaces the default \"general\"."New value: +"Domain, e.g. \"proyectos-web\". Applied when the neuron is created; on an existing neuron it only replaces the default \"general\" (crbro_revise domain replaces it unconditionally)."

addedInput schema / properties / keywords_replace

Added value: +{
+  "description": "When the exact fact text already exists, replace its stored keywords with `keywords` instead of merging (default false). Teammates in a shared space only ever receive the union.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 3, 2026

addedInput schema / properties / keywords

Added value: +{
+  "description": "Facts only. 2-5 words a future question may use that the text does not contain: synonyms, the other language, the generic name of the product named. Indexed with the fact, never shown. The same text again with new keywords merges them.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed9 schema fields changedv1.14.0Sep 3, 2026

changedInput schema / properties / confidence / description

Previous value: -"Confidence level 0.0-1.0 (default 1.0)"New value: +"0.0-1.0, default 1.0. Facts only."

changedInput schema / properties / content / description

Previous value: -"The knowledge content to remember"New value: +"The knowledge itself. Dense and self-contained: it is recalled without this conversation as context."

changedInput schema / properties / domain / description

Previous value: -"Domain category (e.g., \"proyectos-web\", \"infraestructura\")"New value: +"Domain, e.g. \"proyectos-web\". Applied when the neuron is created; on an existing neuron it only replaces the default \"general\"."

addedInput schema / properties / neuron_id

Added value: +{
+  "description": "Exact neuron id from crbro_recall, e.g. \"project_octochat\". Skips name matching entirely.",
+  "type": "string"
+}

changedInput schema / properties / rationale / description

Previous value: -"Rationale for decisions"New value: +"Why the decision was taken. Stored and indexed with it; ignored for other types."

addedInput schema / properties / supersedes

Added value: +{
+  "description": "Facts this one replaces: their ids or exact text. They leave recall but stay in the file. Unmatched targets are reported and stay live.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / topic / description

Previous value: -"The topic name (e.g., \"OctoChat\", \"Firebase\", \"SEO Strategy\")"New value: +"Topic name, e.g. \"OctoChat\", \"Firebase\", \"SEO Strategy\"."

changedInput schema / properties / type / description

Previous value: -"Type of knowledge to store"New value: +"error = a mistake plus its correction, in one entry. debt = a deliberate deferral: what was NOT done on purpose, its ceiling, and the revisit condition, e.g. \"DEFERRED: protecting the PDFs. CEILING: anyone can download them without signing up. REVISIT WHEN: the signup flow works.\""

changedInput schema / properties / type / enum

Previous value: -[
-  "fact",
-  "decision",
-  "pattern",
-  "preference"
-]New value: +[
+  "fact",
+  "decision",
+  "pattern",
+  "preference",
+  "error",
+  "debt"
+]

First observedv1.4.0Aug 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare the generic mutation safety profile, but the description discloses deduplication semantics (keywords merge, updated_in_place), refusal on retired text (skipped_retired), append-only decisions, machine-local preferences, and credential redaction. It also enumerates the return fields, none of which is derivable from annotations.

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 operation with 'Write:' and every subsequent clause carries distinct behavioral information. It is dense and run-on with heavy parentheticals, which slightly hurts scanability, but there is little filler to cut.

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?

With no output schema, the description compensates by listing the return payload (neuron_id, action, superseded count, near_duplicates, etc.) and covers credential handling, dedup, and lifecycle interaction. An agent has everything needed to invoke it correctly.

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 the schema already documents the nuanced behaviors (supersedes staying in the file, keywords_replace default, confidence updated_in_place). The description largely echoes those semantics rather than adding parameter meaning beyond the schema, so the baseline 3 applies.

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?

Opens with a specific verb+resource label ('Write: store a fact, decision, pattern...') and names the exact resource lifecycle it belongs to. It distinguishes itself from siblings by explicitly contrasting crbro_revise, crbro_forget, and crbro_recall within the same paragraph.

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 routing: use crbro_learn with supersedes to replace a truth, crbro_revise to retire without replacement, crbro_forget to delete from disk, and crbro_recall first because the fact may already exist. Preconditions and alternatives are stated, not inferred.

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

Deploy Server

Learn something

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools