Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Share a project

crbro_share

Share or unshare a memory neuron in a team space: dry-run first to detect credentials, then confirm to sync future project notes; unshare stops future sharing.

Instructions

Write: put one neuron into a team space, or take it out with unshare. Call it without confirm first: the dry run reports what would be sent — ops_to_emit, skipped_preferences (preferences never leave this machine) — and refuses outright if it finds a credential (crbro_forget it and rotate it). Show the user, get agreement, call again with the confirm token; a stale token is refused. Entries go out on the next crbro_space action=sync or consolidate, and from then on everything learned about that project flows to the team. unshare stops future notes; what was already sent stays in the remote and in teammates' brains. Spaces are managed with crbro_space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNoSpace name, as created or joined with crbro_space. Required unless unshare:true.
neuronYesNeuron id or name to share or unshare.
confirmNoThe confirm_token from the dry run — returned only when no credential was found. Omit the first time. Ignored with unshare.
unshareNoStop following `neuron` in its space: no more notes go out, the next sync ignores it, and the neuron can then be forgotten. Already-sent notes stay in the remote and in teammates' brains. space and confirm are ignored in this mode.

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. Changed5 schema fields changedv2.0.0
    • changedInput schema / properties / confirm / description
      Previous value: -"The confirm_token from the dry run — returned only when no credential was found. Omit the first time."New value: +"The confirm_token from the dry run — returned only when no credential was found. Omit the first time. Ignored with unshare."
    • changedInput schema / properties / neuron / description
      Previous value: -"Neuron id or name to share."New value: +"Neuron id or name to share or unshare."
    • changedInput schema / properties / space / description
      Previous value: -"Space name, as created or joined with crbro_space."New value: +"Space name, as created or joined with crbro_space. Required unless unshare:true."
    • addedInput schema / properties / unshare
      Added value: +{
+  "description": "Stop following `neuron` in its space: no more notes go out, the next sync ignores it, and the neuron can then be forgotten. Already-sent notes stay in the remote and in teammates' brains. space and confirm are ignored in this mode.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "neuron",
-  "space"
-]New value: +[
+  "neuron"
+]
  3. Addedv1.14.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare a write, open-world, non-idempotent, non-destructive operation. The description adds substantial context beyond them: dry-run outputs, skipped preferences, credential refusal and rotation, confirm-token staleness, sync/consolidate timing, and the lasting effect of already-sent data after unshare.

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 write/dry-run/confirm flow is front-loaded, followed by sync behavior, unshare effects, and sibling routing. It is dense but every sentence carries operational meaning, with no wasted preamble.

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 sharing tool with no output schema, the description covers the full lifecycle: dry run, confirmation, credential handling, sync timing, unshare consequences, and the related crbro_space tool. Nothing essential for correct invocation is missing.

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%, so every parameter is already explained in the input schema. The description reinforces the confirm workflow and unshare behavior but adds little parameter-specific meaning beyond what the schema already provides.

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 specific verb and resource: putting a neuron into a team space, with the inverse unshare mode. It also distinguishes itself from crbro_space, which manages spaces rather than sharing neurons.

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 an explicit call sequence: first without confirm for a dry run, show the user, get agreement, then call again with the confirm token; stale tokens are refused. It also explains when to use unshare and points to crbro_space for space management.

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