Skip to main content
Glama

Broadcast message

broadcast

Send a message from the calling agent to every other member of its team across all devices, with optional auto-poke wake-up hints. Read replies in each agent's inbox.

Instructions

Same-team broadcast to every other agent in the caller team across all devices; delivers to every team member except the sender. Auto-poke default true (quiet-guard + 30s/180s/600s retry; reports poked, poke_skip_reasons, retry_scheduled, retry_delays_s). auto_poke:false opts out. For role filter use broadcast_to_role. For cross-team 1→1 use send_message({to_team}). Auto-poke injects only a SHORT wake-up hint (新邮件 from , 请调 get_inbox 查看) — never the body. Read via get_inbox. Delivery is NOT filtered by online/idle; offline targets still receive mailbox rows. The list_agents online flag reflects process liveness.

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": {
      "body": "<body>"
    },
    "name": "broadcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
subjectNo
auto_pokeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 auto-poke default, the quiet-guard plus 30s/180s/600s retry schedule, the exact contents of the injected wake-up hint ('never the body'), and the returned fields (poked, poke_skip_reasons, retry_scheduled, retry_delays_s). It also preempts a wrong assumption by stating delivery is NOT filtered by online/idle and that list_agents' online flag is process liveness only.

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?

Purpose is front-loaded in the first sentence and nearly every clause carries real information, including the return-field list that substitutes for a missing output schema. It is dense and somewhat run-on, with double spaces and a side remark about list_agents' online flag, but little is truly wasted.

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 3-parameter tool with no annotations and no output schema, the definition covers the key gaps: side effects on recipients, retry behavior, reported result fields, delivery semantics for offline teammates, and the follow-up path (get_inbox). An agent can call and interpret this tool without further context.

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?

Schema coverage is 0%, so the description must compensate and it only partly does: auto_poke is well specified (default true, false opts out, retry consequences) and body is implicitly the message content, but subject is never mentioned or explained. Roughly two of three parameters receive meaning beyond the bare schema.

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, and scope: 'Same-team broadcast to every other agent in the caller team across all devices', and explicitly excludes the sender. It names and distinguishes the two nearest alternatives (broadcast_to_role for role filtering, send_message for cross-team 1→1), so an agent can route correctly 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?

Gives explicit routing rules: use broadcast_to_role when a role filter is needed, use send_message({to_team}) for cross-team 1→1, and read replies via get_inbox. It also states how to opt out of the default behavior (auto_poke:false), which is the main invocation decision for this tool.

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