Skip to main content
Glama

Pace and limits of broadcasts

dosai_get_broadcast_settings
Read-onlyIdempotent

How broadcasts of this project are paced: daily_cap (messages a day), warmup_ramp (lower caps for the first days), send_delay_min_s / send_delay_max_s (pause between messages), window_days (only people who wrote within this many days), max_unanswered, cooldown_days, and the safety stop (breaker_*: the share of undelivered or unsubscribed that pauses a broadcast). Also the platform defaults and the limits a setting cannot exceed.

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_get_broadcast_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.

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.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), and the description goes further by disclosing that the response includes platform defaults and the maximum values a setting cannot exceed — genuinely useful context for a read tool. It stops short of saying how defaults are distinguished from current values in the payload.

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?

One front-loaded sentence that packs only operative content — every clause documents a returned field, so nothing is filler. It is a long run-on list rather than a scannable enumeration, which slightly hurts readability but not economy.

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?

With no output schema, the description correctly carries the burden of describing return values and does so field by field, plus defaults and limits. It is nearly complete; minor gaps remain such as units for cooldown_days/max_unanswered and whether defaults are returned alongside effective values.

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?

There is a single parameter with 100% schema description coverage pointing to dosai_list_projects for the UUID. The description adds nothing about project_id, so the baseline 3 applies since the schema already does the work.

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?

The description names the resource (broadcast pacing/limits for a project) and enumerates the concrete fields it returns, so the agent knows exactly what content to expect. It implicitly contrasts with the sibling dosai_update_broadcast_settings by describing values rather than mutations, though it never states a verb such as 'read' or explicitly names the write counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the read path for settings that dosai_update_broadcast_settings would change, and that the returned 'platform defaults and limits' are useful before editing. There is no explicit when-to-use statement, no named alternative, and no exclusion.

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