Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Connect two neurons

crbro_connect
Destructive

Create, strengthen, or delete a synapse between two validated memory neurons. This defines explicit relationships like dependency, causality, or hierarchy beyond automatic co-occurrence.

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

  1. 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"
+]
  2. 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."
  3. First observedv1.4.0

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses behaviors well beyond the destructiveHint=true annotation: disconnect deletes and unlinks, repeated connects add +0.1 capped at 1.0, idle synapses decay, and absent synapses return action:absent rather than erroring. It also states that an absolute strength can override the default rule, giving the agent a clear mental model of side effects.

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 sentence earns its place: purpose, defaults, destructive behavior, consolidation alternative, read alternative, and return value. It is front-loaded with the write semantics and uses compact, structured phrasing rather than filler.

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 tool with two actions, six parameters, validation semantics, and destructive potential, the description covers the full behavioral surface: creation, strengthening, deletion, absent handling, return values, and relationship to sibling tools. No critical calling context 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 every parameter is already documented in the schema. The description adds meaningful behavioral semantics on top, such as connect defaulting to strength 0.5 with +0.1 increments, disconnect being destructive, and strength overriding the default rule, which is valuable for correct invocation.

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 'Write: create, strengthen or delete the undirected synapse between two neurons', giving a specific verb, resource, and the three actions it supports. It is clearly distinguished from siblings by framing it as a write operation while routing reads to crbro_inspect.

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?

It explicitly contrasts with crbro_consolidate ('so use this for relationships beyond co-occurrence'), with crbro_maintenance for pruning, and with crbro_inspect for reading connections. It also clarifies when to use connect vs disconnect, including the default and side effects, leaving little to inference.

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