Skip to main content
Glama

Message another agent session on this project — live, idle, or recently closed (one-time note, not a brain card)

brain_message

Sends a directed note to another agent session, delivering it on that session's next action even if it is idle or offline. Use it to hand off context between agents instead of asking a human to relay it.

Instructions

Leave a DELIBERATE, targeted note for another agent session working on this project ("merged the hook refactor — rebase before you commit", "don't touch canvasStore, mid-refactor"). Address it to a session id from the brain_sync peer list or brain_doctor. A LIVE session gets it on its next lifecycle event or KLYPIX tool call, even if it is idle right now. A session KLYPIX has identified before that is NOT on the lane now (closed, or quiet) still receives a directed note the moment it next acts — the note is kept for up to 7 days — so if you would otherwise ask the human to relay or paste something to another agent session, send it here instead and tell them it was sent or queued. If the human wants a queued note handled sooner, brain_reopen asks them whether to reopen that session now. Broadcasts ("all") reach only sessions live right now. Any MCP client can send and receive through the shared machine-local presence lane. Delivery contract: a supported action offers the note into model-visible context, a later independent action acknowledges it, and it retires either by an explicit brain_message_receipt ("acted on it") or by auto-consumption on a further independent action; your receipt line names which, and neither is proof a human read it. Expiry or capacity loss leaves a failed per-recipient receipt instead of silently disappearing. OS-user-local and machine-local; with KLYPIX network installed on both computers, a session on another computer in the same project is reached too (its id starts with net:, and there is no read receipt across computers). Ephemeral and NOT persisted to the brain — for a durable decision use brain_note instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "brain_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget — a session id (or unique prefix of at least 8 characters) from the peer list, or an exact unique branch; omit or "all" for every session live right now. A directed id may name a session that is not running: the note then waits and is delivered when that session next starts.
textYesThe note to deliver (kept to 400 chars).
canvasNoBrain canvas filename/path. Defaults to the project brain ("brain").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.89.0
    • changedInput schema / properties / to / description
      Previous value: -"Target hint — a peer session id-prefix or branch name; omit or \"all\" for every live session."New value: +"Target — a session id (or unique prefix of at least 8 characters) from the peer list, or an exact unique branch; omit or \"all\" for every session live right now. A directed id may name a session that is not running: the note then waits and is delivered when that session next starts."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses live/idle delivery, up-to-7-day retention for directed notes, broadcast scope, delivery/acknowledgement/retirement mechanics, receipt behavior, failure receipts, machine-local scope, cross-computer limits, and the absence of read receipts across computers.

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?

It is front-loaded with the main action and target before moving into delivery mechanics. The length is justified by the tool's complexity, though some phrasing is dense and slightly repetitive around delivery and receipt behavior.

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 annotations and no output schema, the description is unusually complete: it covers routing, retention, delivery outcomes, acknowledgement, failure modes, scope, and the ephemeral versus durable distinction. An agent has enough information to call and interpret the tool 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 already 100%, so the baseline would be 3. The description nevertheless adds operational meaning to the target parameter: session ids can come from brain_sync or brain_doctor, directed notes may wait for non-running sessions, and 'all' reaches only sessions live right now.

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 states a specific verb and resource: leave a deliberate targeted note for another agent session on the project. It explicitly distinguishes this from brain_note by saying this is ephemeral and not persisted, while brain_note is for durable decisions.

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 concrete when-to-use guidance, including replacing human relay: 'if you would otherwise ask the human to relay or paste something to another agent session, send it here instead.' It also names alternatives: brain_note for durable decisions and brain_reopen for handling queued notes sooner.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.