Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Team space

crbro_space

Create, join, sync, status, or leave shared team spaces—a private git repository for notes teammates choose to share. Manage project-specific memory together without exposing personal brain data.

Instructions

Read or write team spaces — shared memory with teammates: a private git repository holding notes about the projects you choose to share; nothing else from your brain goes near it. create starts one (name, remote, author); join clones one a teammate created; status reads your identity and spaces; sync exchanges notes now — the manual form of what crbro_boot and crbro_consolidate do alone, useful right after crbro_share (offline is a normal answer, not a failure); leave pushes pending notes, deletes the local copy and stops following its neurons (neurons untouched). Joining shares nothing: put each project in with crbro_share. create and join reply ok:false with the reason on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoShort name, e.g. "equipo" — the same on everyone's machine. Required for create, join and leave; optional for sync (omit = every space); ignored for status.
actionYescreate = start a new space and push it; join = clone one a teammate created; status = your identity and spaces; sync = exchange notes now; leave = sync, then forget the space locally.
authorNoHow your notes are signed, e.g. "ana". Lowercase, no spaces. Required for create and join.
branchNoBranch to use (default "main"). create and join only.
remoteNoGit URL of a private repository — EMPTY for create, the same URL the creator used for join. E.g. git@github.com:acme/team-memory.git.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / properties / action / description
      Previous value: -"create = start a new space and push it, join = clone one a teammate created, status = your identity and the spaces you are in."New value: +"create = start a new space and push it; join = clone one a teammate created; status = your identity and spaces; sync = exchange notes now; leave = sync, then forget the space locally."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "create",
-  "join",
-  "status"
-]New value: +[
+  "create",
+  "join",
+  "status",
+  "sync",
+  "leave"
+]
    • changedInput schema / properties / branch / description
      Previous value: -"Branch to use (default \"main\")."New value: +"Branch to use (default \"main\"). create and join only."
    • changedInput schema / properties / name / description
      Previous value: -"Short name, e.g. \"equipo\" — the same on everyone's machine. Required for create and join."New value: +"Short name, e.g. \"equipo\" — the same on everyone's machine. Required for create, join and leave; optional for sync (omit = every space); ignored for status."
  2. Addedv1.14.0

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the annotations by explaining the privacy boundary ('nothing else from your brain goes near it'), the side effects of leave ('pushes pending notes, deletes the local copy... neurons untouched'), and the offline behavior ('offline is a normal answer, not a failure'). These are behavioral facts an agent could not derive from structured fields.

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?

The description is dense and front-loaded, with each clause earning its place and no filler. It is long, but the tool has five subcommands and multiple cross-tool relationships to cover.

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?

Given no output schema, it still conveys failure shape ('create and join reply ok:false with the reason'), sync semantics, and side effects. Combined with the comprehensive input schema, an agent has enough context to invoke every action 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 coverage is 100% and each parameter already has action-specific descriptions. The description reinforces that name, remote, and author matter for create/join, but it adds little new meaning beyond what the schema 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?

The description names a concrete resource ('team spaces' as shared git repositories) and enumerates five discrete actions with their effects: create, join, status, sync, leave. This makes it immediately distinguishable from siblings such as crbro_share, which is referenced for a different purpose.

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 gives explicit routing: sync is 'the manual form of what crbro_boot and crbro_consolidate do alone, useful right after crbro_share', and 'Joining shares nothing: put each project in with crbro_share'. This tells an agent when to reach for this tool versus named alternatives.

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