Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

create_broadcast

Create a DRAFT broadcast for an agent (does not dial anyone). Configure schedule window, retries, and the per-call prompt template with {{variables}}.

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": {
      "agent_id": "<agent_id>",
      "prompt_template": "<prompt_template>"
    },
    "name": "create_broadcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNooptional label (avoid PII)
purposeNoRequired on tools that read data or reports; recommended on every tool. One sentence: what you are doing and why (for example "finding this caller's open ticket to answer them"). Building a report, dashboard, analytics or an export is a SautiDesk Pro feature done by the report tools, not by pulling records.
agent_idYesagent UUID that will speak on each call
retry_onNooutcomes that trigger a retry: no_answer, busy, failed, voicemail
timezoneNoIANA timezone for the schedule window, e.g. Africa/Nairobi
max_attemptsNoattempts per contact before giving up
start_phraseNoopening line the agent speaks first
schedule_daysNodays of week the broadcast may dial (0=Sunday..6=Saturday)
backoff_minutesNowait between retry attempts
prompt_templateYesper-call prompt; {{variable}} placeholders are filled from each contact's variables
caller_number_idNoworkspace number UUID to dial from
daily_end_minuteNolatest dial time as minutes after midnight
daily_start_minuteNoearliest dial time as minutes after midnight

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover openWorldHint=false and destructiveHint=false, so the description carries the meaningful behavioral load and does it well: the object is created in DRAFT state and no calls are placed, which is the single most important fact for an agent to know before invoking this. It stops short of saying whether contacts must be attached before the draft can be started, or what identifier comes back, but the core behavioral disclosure is present.

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?

Two sentences, zero filler, and the most decision-relevant fact (DRAFT, no dialing) is front-loaded before the configuration summary. Nothing in it restates the tool name or wastes a clause.

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 13-parameter creation tool with no output schema and thin annotations, the description covers purpose, draft state, and the main configuration axes adequately. The remaining gaps are the expected return value (a broadcast id) and the relationship to add_broadcast_contacts and start_broadcast, which a multi-step broadcast workflow would benefit from.

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 description coverage is 100%, so the per-parameter definitions already do the heavy lifting and the baseline is 3. The description adds a light but real layer by clustering the 13 parameters into three concerns — schedule window, retries, and the per-call prompt template with {{variables}} — which helps an agent reason about the configuration surface as a whole rather than 13 independent fields.

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?

States a specific verb and resource ('Create a DRAFT broadcast') and immediately bounds scope with 'for an agent (does not dial anyone)'. That parenthetical alone separates it from start_broadcast, pause_broadcast, and resume_broadcast in the sibling list without the agent needing 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 Guidelines3/5

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

The 'does not dial anyone' clause implicitly tells the agent this is the setup step and that dialing happens elsewhere, but it never names start_broadcast or add_broadcast_contacts as the follow-on calls. No explicit when-to-use, when-not-to-use, or prerequisite statement is given, so the routing is inferred rather than stated.

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

All Sautikit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources