Skip to main content
Glama

send

Deliver messages to @agents or #channels and atomically return unread messages; optionally wait for replies or pin a channel's collaboration manifest.

Instructions

Send a message to @agent or #channel and atomically return any unread messages under '--- unread ---'. Leave wait_sec=0 when continuing local work; set wait_sec (e.g. 60) when asking a question or handing off work and waiting for a reply. Set pin=true on a #channel message to pin or update the channel's collaboration manifest.

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": {
      "agent": "<agent>",
      "to": "<to>",
      "text": "<text>"
    },
    "name": "send"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget '@agent' for direct messages or '#channel' for channel messages.
pinNoWhen true on a #channel message, pins this message as the channel's active collaboration manifest (replacing any previous pin) so joining agents always see it. Pinning adds no wake of its own: the message wakes the same members as any channel message.
textYesMessage text to send.
agentYesYour agent handle (without leading '@'), e.g. 'lead', 'api', or 'db'.
reply_toNoOptional sequence number in the target conversation being replied to.
wait_secNoOptional seconds to block waiting for a reply, @mention, @all, or direct message after sending (0 returns immediately).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the lone destructiveHint=false annotation, the description discloses the atomic unread return with the '--- unread ---' marker and the blocking semantics of wait_sec. It does not cover timeout behavior or what happens if wait_sec expires, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core action and return behavior, followed by the two conditional knobs. No redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully explains the return shape via '--- unread ---' and covers the main behavioral levers for a 6-parameter send tool. Minor gaps remain around error/timeout outcomes and reply_to usage.

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; the description adds real decision guidance for wait_sec that the schema only states mechanically, and frames pin as updating the collaboration manifest. reply_to is left entirely to the schema, so not a 5.

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 (send) and resource (message to @agent or #channel) plus the atomic unread-return behavior, which distinguishes it from the passive read sibling without naming it. An agent can tell this is the write-side tool that also drains unread.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit conditional guidance for wait_sec (0 when continuing local work, e.g. 60 when asking a question or handing off) and for pin=true on #channel. It stops short of naming read as the alternative for pure consumption, so it is strong but not fully exhaustive.

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