Skip to main content
Glama

leave_note

Send a message to another agent - a named peer or the next workspace visitor - and start a new thread or reply to an existing one. Recipients retrieve notes by polling.

Instructions

Send a message to another agent — a named peer session, or "next" (whoever attaches to this workspace next). Send half of plumb's mailbox; check_messages is the receive half. Full etiquette — addressing, delivery, the exchange cap, cross-project rules: the plumb-chat skill.

Every message belongs to a thread: omit conversation_id to start one (the reply carries its id), or quote an id you were given to reply into that thread (to may then be omitted). A thread is capped at [collab] max_exchanges messages; once spent, replies are refused.

Delivery is by polling only, exactly once — via the next tool call, check_messages, or session_start. A peer idle on its human has not seen the message; silence is not refusal, so do not re-send.

Messages are bound to the exact SESSION when it is connected; a disconnected peer, or "next", is delivered by name instead. Cross-project sends need the recipient project's opt-in. Requires [collab] mailbox = true; the body is secret-scrubbed.

Parameters: body (required); to (peer session name or "next" — omitted means "next" on a new thread, the other participant on a reply); conversation_id (reply into an existing thread).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoA peer session name, or "next" for whoever attaches to this workspace next. Omitting it defaults to "next" when you are starting a thread; when you pass a conversation_id it instead resolves to that thread's other participant, and the send is refused if the thread has no other participant or more than one. A name belonging to a session in another workspace is refused up front unless that project has already opted in to cross-project messages.
bodyYesThe message to send (free text).
conversation_idNoReply into an existing thread by quoting the conversation id you were given. Omit to start a new thread.

Schema Changelog

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

  1. Changed1 schema field changedv0.17.0
    • changedInput schema / properties / to / description
      Previous value: -"A peer session name, or \"next\" (default) for whoever attaches to this workspace next. A name belonging to a session in another workspace is delivered only if that project allows cross-project messages."New value: +"A peer session name, or \"next\" for whoever attaches to this workspace next. Omitting it defaults to \"next\" when you are starting a thread; when you pass a conversation_id it instead resolves to that thread's other participant, and the send is refused if the thread has no other participant or more than one. A name belonging to a session in another workspace is refused up front unless that project has already opted in to cross-project messages."
  2. First observedv0.16.6

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden. It richly discloses delivery semantics (polling, exactly once, via next tool call/check_messages/session_start), session binding, 'silence is not refusal', the thread cap, and the secret-scrubbing requirement. This goes far beyond what the schema reveals.

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 long but every sentence serves a purpose, covering addressing, threads, delivery, permissions, and configuration. The final 'Parameters:' paragraph is partially redundant with the schema, but it also provides a quick-reference summary without bloating the overall structure.

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?

The description covers nearly all practical invocation details: how to start or reply to a thread, what 'next' means, when re-sending is prohibited, what happens when the thread cap is reached, and the permission/config prerequisites. It even hints at the relevant return payload by saying the reply carries the conversation id, compensating for the absence of an output schema.

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?

The input schema already describes all three parameters at 100% coverage, so the description's parameter summary adds little new information. It does reinforce the 'reply carries its id' behavior and the omitted-default of 'next', but the schema contains these same nuances. A baseline 3 is appropriate given the high schema coverage.

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 opens with a specific action — 'Send a message to another agent' — and clearly distinguishes it from check_messages, the receive half. It also names the two addressing modes, 'named peer session' and 'next', so an agent immediately knows what the tool is for.

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?

The description explicitly identifies check_messages as the counterpart for receiving, and specifies when to use 'to', when to omit it, and how conversation_id starts or continues a thread. It also covers prerequisites such as cross-project opt-in and the mailbox requirement, leaving little ambiguity about when the tool is appropriate.

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

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/plumbkit/plumb'

If you have feedback or need assistance with the MCP directory API, please join our Discord server