Skip to main content
Glama

Cancel a broadcast for good

dosai_stop_broadcast
Destructive

Cancel a broadcast that is scheduled, queued, being sent or paused (ids: dosai_list_broadcasts): clients who have not received it yet will not. Already sent messages stay. It CANNOT be resumed afterwards, a new broadcast would have to be created. Two steps. Requires admin or owner 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": {
      "project_id": "<project_id>",
      "broadcast_id": "<broadcast_id>"
    },
    "name": "dosai_stop_broadcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
broadcast_idYes
confirm_tokenNoLeave empty on the first call: it changes nothing and returns what will happen and a code. Ask the owner; only after their explicit "yes" call again with the same arguments and this code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed2 schema fields changed
    • removedInput schema / properties / broadcast_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description spells out the consequence precisely: unsent recipients will not receive it, already-sent messages remain, and the action cannot be undone or resumed without creating a new broadcast. It also discloses the two-step confirmation and the role requirement, which are real behavioral constraints an agent must plan for.

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 text is short and front-loads the scope of what can be cancelled before the consequences. Some phrasing is clipped ("clients who have not received it yet will not") and the "Two steps" sentence is terse to the point of being cryptic, but nothing is padded.

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 destructive, irreversible mutation with no output schema, the description covers consequences, irreversibility, confirmation, and permissions, which is what an agent needs to call it safely. It omits what the first confirmation call returns, though the schema hints at a code being returned.

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 67%, and the description fills one of the gaps by stating that broadcast ids come from dosai_list_broadcasts, while project_id's source is already documented in the schema. The confirm_token flow is only alluded to as "Two steps" rather than explained, but the schema itself documents that parameter in detail.

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 states a specific verb and resource (cancel a broadcast) and enumerates the exact states it applies to (scheduled, queued, being sent, paused), which separates it from siblings like dosai_resume_broadcast and dosai_cancel_scheduled_message. It also names the tool that supplies the ids (dosai_list_broadcasts).

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 gives clear conditions for use — the broadcast must be in one of four states — plus the prerequisite of admin or owner role and the two-step confirmation flow. It does not explicitly name an alternative tool to use instead for other cases, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources