Skip to main content
Glama

Broadcast to role

broadcast_to_role

Broadcast a message to every same-team agent matching a role across all devices, with an optional short wake-up hint; recipients read the message from their inbox.

Instructions

Same-team broadcast filtered by role across all devices; delivers to every matching team member. Strictly same-team — no cross-team variant. For cross-team private 1→1 use send_message({to_team}). Auto-poke default true with quiet-guard + 30s/180s/600s retry (auto_poke:false opts out); injects only a SHORT wake-up hint, not the message body. Recipients read via get_inbox. Returns unknown_recipient when no same-team agent matches to_role.

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

Input Schema

NameRequiredDescriptionDefault
bodyYes
subjectNo
to_roleYes
auto_pokeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the whole burden and does substantial work: auto_poke defaults to true, the quiet-guard plus 30s/180s/600s retry schedule, the auto_poke:false opt-out, and the fact that only a short wake-up hint (not the body) is injected. It also documents the error contract (returns unknown_recipient when no same-team agent matches) and that recipients read via get_inbox. It does not cover authentication/registration prerequisites or rate limits, which keeps it below 5.

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 purpose is front-loaded and every sentence adds new information, but the dense semicolon-and-parenthetical style makes it read as a run-on, and the ordering bounces between scope, alternatives, poke semantics, and error codes rather than grouping them.

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?

For a 4-parameter mutation-ish delivery tool with no annotations and no output schema, the definition covers delivery semantics, retry/quiet-guard behavior, the read path (get_inbox), and the primary error case. The only meaningful hole is the undocumented 'subject' parameter and the absence of any note on prerequisites for being a valid recipient.

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 description coverage is 0%, so the description must compensate. It explains to_role (role filter plus the unknown_recipient failure mode) and auto_poke (default true, opt-out), and implicitly what body is ('not the message body' is injected as a hint). The 'subject' parameter is never mentioned anywhere, leaving one of four parameters undocumented in both schema and prose.

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 gives a specific verb and resource ('same-team broadcast filtered by role across all devices; delivers to every matching team member'), which lets an agent distinguish it from plain broadcast and from send_message without opening either schema. Scope ('strictly same-team') is stated up front.

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?

It names the alternative for a different need ('For cross-team private 1→1 use send_message({to_team})') and rules out a cross-team variant. It stops short of contrasting with the sibling 'broadcast' tool for the unfiltered case, so the routing guidance is strong but not exhaustive.

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