Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Connect two neurons

crbro_connect
Destructive

Create, strengthen, or delete an undirected synapse between two memory neurons. Set relationship type, context, and strength to model dependencies, causes, or hierarchies.

Instructions

Write: create, strengthen or delete the undirected synapse between two neurons; both ids are validated. action=connect (default) creates at strength 0.5 and adds +0.1 per repeat call (cap 1.0), or sets the absolute strength you pass; action=disconnect deletes the synapse and unlinks both neurons — the destructive side. Idle synapses decay and crbro_maintenance prunes the weak; crbro_consolidate links neurons written in the same session by itself, so use this for relationships beyond co-occurrence. To read connections use crbro_inspect view=neuron. Returns synapse_id, action (created|strengthened|disconnected|absent) and strength.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesExact neuron id. Order does not matter — (a,b) and (b,a) are the same synapse.
fromYesExact neuron id, e.g. "project_octochat". Validated: an unknown id is an error.
typeNoRelationship kind, used only when the synapse is created (default conceptual). Ignored on strengthen and on disconnect.
actionNoconnect = create or strengthen (default); disconnect = delete the synapse and unlink both neurons. An absent synapse returns action:absent, removed:false, not an error.
contextNoOne line on the relationship. On strengthen it replaces the stored text; omit to keep it.
strengthNoAbsolute strength 0.0-1.0 to set, on create or on an existing synapse, instead of the 0.5 / +0.1 rule.

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. Changed6 schema fields changedv2.0.0
    • addedInput schema / properties / action
      Added value: +{
+  "description": "connect = create or strengthen (default); disconnect = delete the synapse and unlink both neurons. An absent synapse returns action:absent, removed:false, not an error.",
+  "enum": [
+    "connect",
+    "disconnect"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / from / description
      Previous value: -"Source neuron id, e.g. \"project_octochat\". Not validated: use an exact id from crbro_recall or crbro_neurons, or the synapse points at nothing."New value: +"Exact neuron id, e.g. \"project_octochat\". Validated: an unknown id is an error."
    • addedInput schema / properties / strength
      Added value: +{
+  "description": "Absolute strength 0.0-1.0 to set, on create or on an existing synapse, instead of the 0.5 / +0.1 rule.",
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}
    • changedInput schema / properties / to / description
      Previous value: -"Target neuron id. Order does not matter — (a,b) and (b,a) are the same synapse."New value: +"Exact neuron id. Order does not matter — (a,b) and (b,a) are the same synapse."
    • changedInput schema / properties / type / description
      Previous value: -"Relationship kind. Used only on creation; a strengthening call keeps the existing type."New value: +"Relationship kind, used only when the synapse is created (default conceptual). Ignored on strengthen and on disconnect."
    • changedInput schema / required
      Previous value: -[
-  "from",
-  "to",
-  "type"
-]New value: +[
+  "from",
+  "to"
+]
  3. Changed4 schema fields changedv1.14.0
    • changedInput schema / properties / context / description
      Previous value: -"Description of the relationship"New value: +"One line on the relationship. On strengthen it replaces the stored text; omit to keep it."
    • changedInput schema / properties / from / description
      Previous value: -"Source neuron ID"New value: +"Source neuron id, e.g. \"project_octochat\". Not validated: use an exact id from crbro_recall or crbro_neurons, or the synapse points at nothing."
    • changedInput schema / properties / to / description
      Previous value: -"Target neuron ID"New value: +"Target neuron id. Order does not matter — (a,b) and (b,a) are the same synapse."
    • changedInput schema / properties / type / description
      Previous value: -"Connection type"New value: +"Relationship kind. Used only on creation; a strengthening call keeps the existing type."
  4. First observedv1.4.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description explains *why* it is non-idempotent (+0.1 per repeat call, cap 1.0), labels disconnect as 'the destructive side', notes both neurons are unlinked, and states that validation errors on unknown ids. It even discloses the return shape (synapse_id, action, strength) despite no output schema.

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-loaded with 'Write:' and every clause carries information about behavior or routing. It is dense and semicolon-heavy, and some sentences (type ignored on strengthen/disconnect, action enum meanings) merely mirror the schema, adding length without new signal.

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?

Covers the full call contract: defaults, strengthen arithmetic, disconnect semantics, validation failure mode, absent-synapse non-error behavior, and return fields. With six parameters and no output schema, nothing an agent needs to invoke or interpret the call 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 the strength rule the schema only alludes to ('0.5 / +0.1 rule'): default 0.5, +0.1 per repeat, cap 1.0, or an absolute override. It also restates enum semantics for action/type, which is duplicative rather than additive.

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 an explicit verb+resource and scope: 'Write: create, strengthen or delete the undirected synapse between two neurons'. It immediately separates itself from crbro_consolidate (co-occurrence linking) and crbro_inspect (reading), so an agent can route without opening the 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 and when-not-to-use: use crbro_consolidate for same-session co-occurrence, use crbro_inspect view=neuron to read, and this tool for relationships beyond co-occurrence. It also names the lifecycle pressures (idle decay, crbro_maintenance pruning) that argue for explicit calls.

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