Skip to main content
Glama
dahshanlabs

klypix-mcp

by dahshanlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

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

brain_message

Send a targeted note to another agent session to hand off context or warnings, delivered now or queued until that session next acts, without human relay.

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. Ephemeral and NOT persisted to the brain — for a durable decision use brain_note instead.

Input Schema

TableJSON 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 burden and does so: it discloses the delivery lifecycle (offered into context, later acknowledged, retired by receipt or auto-consumption), 7-day retention, broadcast scoping, and that expiry leaves a failed receipt rather than silent loss. It also states the tool is ephemeral, OS-user-local, and not persisted.

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-loaded with the action and an illustrative example, and most sentences carry distinct information. It is dense and the receipt/delivery-contract passage is somewhat repetitive, but nothing is padding in the way a vague one-liner would be.

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, unannotated tool with no output schema, the description covers targeting, delivery timing, retention, broadcast scope, receipt semantics, and durability trade-offs — enough for an agent to call it correctly without guessing.

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 the baseline is 3, but the description adds semantics beyond the schema: 'all' or omitted reaches only currently-live sessions, a directed id may wait for a not-yet-running session, and delivery timing differs for live vs. quiet recipients.

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 — leave a deliberate, targeted note for another agent session — and immediately contrasts it with brain_note ('durable decision') and brain_message_receipt, so the agent can place it among siblings without opening a 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?

Gives explicit when-to-use guidance ('if you would otherwise ask the human to relay or paste something... send it here instead'), names the sources for a target id (brain_sync peer list, brain_doctor), and points to 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.

Deploy Server

Other Tools