Skip to main content
Glama

Change the pace of broadcasts

dosai_update_broadcast_settings
Destructive

Change the broadcast pace; pass only what changes. daily_cap 1..3000, send_delay_min_s and send_delay_max_s 8..3600 seconds, window_days 1..90, max_unanswered 0..20 (skip people who left this many of our messages unanswered), cooldown_days 0..365 (rest between broadcasts to one person), breaker_undelivered_pct and breaker_optout_pct 1..100, breaker_window 5..500. Faster and wider than the defaults raises the risk that WhatsApp blocks the owner's number. "Only people who wrote to us" and the sending hours cannot be switched off. The answer is what was saved. 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>"
    },
    "name": "dosai_update_broadcast_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
daily_capNo
project_idYesFrom dosai_list_projects.
window_daysNo
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.
cooldown_daysNo
breaker_windowNo
max_unansweredNo
send_delay_max_sNo
send_delay_min_sNo
breaker_optout_pctNo
breaker_undelivered_pctNo

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. Changed1 schema field changed
    • 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

A3.9/5.0
Behavior4/5

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

Beyond the destructiveHint/readOnlyHint annotations, it discloses operator risk (accelerating pace can get the owner's WhatsApp number blocked), immutables (audience filter and sending hours cannot be disabled), the confirmation-token workflow requiring the owner's explicit "yes", and that the response reflects the saved state. The confirm-token mechanics are mostly carried by the schema description, so the description itself adds less there.

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 core action and partial-update rule are front-loaded, and the rest is packed into a dense but scannable clause list. The parenthetical glosses earn their place, though repeating every min/max value duplicates data already in the schema.

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 an 11-parameter destructive mutation with no output schema, the description covers permissions, risk, immutables, the two-step confirmation requirement, and what the response represents. The main remaining gap is not describing what happens to dependent state (e.g., an in-flight broadcast) when pace changes are applied.

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?

With only 18% schema description coverage across 11 parameters, the description does the heavy lifting by glossing each field's real-world meaning: max_unanswered as people who ignored N messages, cooldown_days as rest between broadcasts to one person, and the breaker percentages as failure thresholds. It also explains that settings not passed are left unchanged. The numeric ranges largely restate schema min/max, and the breaker fields are named without explaining what tripping the breaker actually does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Change the broadcast pace" gives a specific verb plus resource, and "pass only what changes" signals partial-update semantics, which distinguishes it from the read-side get_broadcast_settings without naming it. It stops short of explicitly contrasting with the sibling read/preview tools, so an agent still has to infer that relationship from names.

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 concrete preconditions and context: admin or owner role required, only diff fields should be sent, and the call is a two-step flow with the first call being a no-op preview. It does not explicitly say when to prefer this over sibling settings tools or which settings are out of scope beyond the two named immutables.

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