Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Boot the brain

crbro_boot
Idempotent

Load persistent memory first in every conversation to retrieve hot topics, active context, and protocols. Pass project to prioritize relevant neurons; skipping loses context.

Instructions

Read the brain at session start — call it FIRST in every conversation, before any other work; writes only the boot stamp (and the brain itself on first use). Loads memory from earlier sessions: hot topics, active context with open_items and recently_closed (never report recently_closed as pending; verify open_items before repeating them), recent_sessions, counts, active protocols as a protocol_enforcement block you must follow, memory_discipline (the rules for using this memory well) and retired_tools (old tool names → their replacement). Readies the search index and syncs shared team spaces (offline is normal). Pass project (the working folder or repo name) to put that project's neurons first: project_neurons. Skipping it loses all context; close the session with crbro_consolidate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoThe folder or repository this session works in: a path ("C:/code/crbro-memory"), a repo name or a remote ("owner/repo"); only the last segment counts. Neurons whose name, system map or fact keywords name it come first in hot_topics and are listed in project_neurons (at most 5). Omit it and boot is exactly as without.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.9.1
    • addedInput schema / properties / project
      Added value: +{
+  "description": "The folder or repository this session works in: a path (\"C:/code/crbro-memory\"), a repo name or a remote (\"owner/repo\"); only the last segment counts. Neurons whose name, system map or fact keywords name it come first in hot_topics and are listed in project_neurons (at most 5). Omit it and boot is exactly as without.",
+  "type": "string"
+}
  2. Changed1 schema field changedv2.4.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. First observedv1.4.0

TDQS

A4.8/5.0
Behavior5/5

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

Discloses the write side-effect that explains readOnlyHint=false ('writes only the boot stamp (and the brain itself on first use)'), corroborates the idempotent hint, and adds operational facts beyond annotations: offline is normal, the index is readied, team spaces are synced. It also carries behavioral duties (follow protocol_enforcement, verify open_items, never report recently_closed as pending) that annotations cannot express.

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-loads the imperative ('call it FIRST') and then clusters the return contents efficiently. It is dense and parenthetical-heavy, and a few clauses (e.g., the recent_sessions/counts list) could be trimmed, but almost every sentence earns its place.

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?

No output schema exists, yet the description enumerates what boot returns (hot topics, active context, protocols, retired_tools, etc.) and the follow-up action. For a zero-required-param, single-param tool, an agent has everything needed to call it correctly.

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 baseline is 3, but the description adds real semantics: it explains the payoff of 'project' (its neurons come first via project_neurons, max 5) and that only the last path segment counts. That is genuine value beyond the schema text.

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+resource ('Read the brain at session start') and immediately distinguishes itself from siblings by naming crbro_consolidate as the closing counterpart. An agent can tell this is the session-init memory loader without opening any 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?

Explicit ordering rule ('call it FIRST in every conversation, before any other work') plus the paired closing tool ('close the session with crbro_consolidate'). Leaves no ambiguity about when to invoke it versus other crbro tools.

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