Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

System map

crbro_map
DestructiveIdempotent

Read or replace a neuron's system map—a living document of layout, dependencies, and pitfalls. Use it before working on a system from past sessions, then rewrite after changes.

Instructions

Read or replace a neuron's system map: ONE living document — where the system lives, what serves what, which pieces talk to each other, the traps that cost hours. crbro_inspect view=neuron already returns the map; use crbro_map to read it alone, or to rewrite it. Omit content to read (map:null if none); content replaces the previous version entirely (append-only maps rot); an empty string clears it. Read it before working on a system touched in past sessions; after changing the system rewrite the whole map. Reading never creates a neuron, writing does. Credentials are redacted on write. Atomic facts belong in crbro_learn — the map is the prose around them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoDomain if the neuron has to be created, e.g. "proyectos-web". Ignored when it exists.
neuronYesNeuron id or name, e.g. "project_octochat" or "OctoChat".
contentNoThe new map, replacing the old one whole; omit to read. Write the reference you will need next time: paths, ids, what-serves-what, gotchas. An empty string clears the map.

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. Addedv1.14.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations flag destructive/idempotent writes, and the description goes well beyond them: it discloses that reading never creates a neuron while writing does, that content replaces the prior version wholesale (with the 'append-only maps rot' rationale), that an empty string clears it, and that credentials are redacted on write. These are exactly the side effects an agent must know before invoking.

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?

Dense and front-loaded: the read/write split leads, then the rules, then the sibling routing. Every clause carries a distinct rule, though the run-on structure and parenthetical asides make it slightly heavier than needed.

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 still supplies the return contract ('map:null if none') and covers both modes, creation side effects, and redaction. Nothing an agent needs to call this correctly is missing.

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 100%, so the baseline is 3, but the description adds real semantics on top: omitting content means read, empty string means clear, and content overwrites wholly. It also clarifies that domain is only used when the neuron must be created, reinforcing the schema's 'ignored when it exists' note.

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 concrete verb pair plus resource ('Read or replace a neuron's system map') and immediately characterizes what the document contains. It explicitly distinguishes itself from crbro_inspect (which returns the map anyway) and from crbro_learn (atomic facts), so an agent can route without opening schemas.

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-read ('before working on a system touched in past sessions'), when-to-write ('after changing the system rewrite the whole map'), and names the alternative path (crbro_inspect view=neuron, crbro_learn). Exclusion guidance is present rather than inferred.

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