Skip to main content
Glama

Continue a broadcast the safety stop paused

dosai_resume_broadcast
Destructive

Continue a broadcast with status paused (dosai_list_broadcasts shows it and paused_reason): the people who have not received it yet will. Nobody gets it twice. The safety stop paused it because too many messages were not delivered or too many people unsubscribed, so find out why before continuing: the same share will pause it again. Messages go to real clients. 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_resume_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.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds the substance behind them: only non-recipients are messaged, no one is double-sent, 'Messages go to real clients,' and an admin/owner role is required. It also discloses the two-step confirm_token gate and the consequence of ignoring the pause reason, which no structured field conveys.

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 key constraint (paused status, undelivered audience) is front-loaded, and later sentences carry real weight: the re-pause warning, the real-clients consequence, the two-step process, the role requirement. It is dense and slightly run-on with its colon-and-clause chaining, but no sentence is 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?

For a three-parameter, destructive, externally-visible mutation with no output schema, the definition covers prerequisites, role, side effects, deduplication guarantees, and the confirmation flow. It does not say what state the broadcast is left in after continuation or how failures surface, which is a modest remaining gap but not one that would cause a wrong call.

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 67% and the schema itself already documents confirm_token thoroughly, including the empty-first-call preview behavior and the explicit owner approval requirement. The description only contributes the hint that broadcast_id comes from dosai_list_broadcasts's paused entries; project_id and the mechanics of the second call add nothing beyond the schema, so baseline 3 is right.

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 on a specific resource and a precise scope: 'Continue a broadcast with status paused ... the people who have not received it yet will. Nobody gets it twice.' That verb+resource+audience triple separates it cleanly from dosai_start_broadcast (new send) and dosai_stop_broadcast (reverse action) without requiring the agent to open 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 Guidelines4/5

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

It states the exact precondition (status paused, verifiable via dosai_list_broadcasts and its paused_reason) and adds a strong when-not-to-rush warning: diagnose the cause first because 'the same share will pause it again.' It stops short of explicitly naming the sibling to use for a fresh send or for resuming under different conditions, so the routing to alternatives is implied rather than spelled out.

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