Skip to main content
Glama

Who would get a broadcast

dosai_preview_broadcast_audience
Read-onlyIdempotent

Count the people a broadcast would reach right now, and who would be skipped and why (no inbound ever, waiting for our reply, wrote too long ago, unsubscribed, got a broadcast recently). Read-only, nothing is sent. Run this before start_broadcast and tell the owner the numbers.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
channelNoDefault: telegram.
project_idYesFrom dosai_list_projects.
lead_statusNo
window_daysNoOnly people who wrote to us within N days. Up to 90.

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally; the description reinforces it with 'nothing is sent'. It adds genuine behavioral value by enumerating the exclusion categories (no inbound ever, awaiting our reply, stale, unsubscribed, recently broadcast), which tells the agent what the result actually means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The count-and-reasons purpose is front-loaded in the first clause, followed by two short supporting sentences covering safety and sequencing. There is no filler or repeated schema information.

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?

There is no output schema, so the description carries the burden of describing returns; it does so by naming the count plus the skip reasons, which is sufficient to interpret a result. Minor gaps remain around whether per-recipient details are returned versus aggregate counts only.

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 60%: channel and window_days are documented inline while tag and lead_status have no schema description. The description gestures at the recency filter ('wrote too long ago', 'got a broadcast recently') but never maps it to window_days or explains tag/lead_status filtering, so it does not fully compensate for the gap.

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 precise verb and resource: 'Count the people a broadcast would reach right now' plus the breakdown of skipped recipients and reasons. It is immediately distinguishable from the sibling start_broadcast, which actually sends, versus this which only previews.

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 an explicit sequencing rule ('Run this before start_broadcast and tell the owner the numbers'), which is exactly the guidance an agent needs. It does not spell out when to skip the preview or how it relates to get_broadcast_settings, so it stops short of full when/when-not coverage.

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