Sautikit

resume_broadcast

Idempotent

SPENDS MONEY: resume a paused broadcast — dialing (and billing) restarts. Confirm with the user first. Optionally reselect the agent or caller number if the originals are gone.

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": {
      "broadcast_id": "<broadcast_id>"
    },
    "name": "resume_broadcast"
  }
}

Input Schema

Name	Required	Description
`purpose`	No	Required 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_id`	No	replacement agent UUID if the original is gone
`broadcast_id`	Yes	broadcast UUID
`caller_number_id`	No	replacement caller number UUID if the original is gone

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: the annotations only say it is non-destructive and idempotent, while the description discloses that money is spent, that billing restarts on dialing, that user confirmation is required, and that agent/number can be swapped if the originals no longer exist. That is exactly the behavioral context an agent needs before a costly mutation.

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?

Three short sentences, with the highest-stakes fact (SPENDS MONEY) front-loaded in capitals, followed by the confirmation requirement and then the optional parameter note. Nothing is wasted.

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 financially consequential mutation with four documented parameters and no output schema, the definition covers cost, confirmation, and parameter fallbacks. It stops short of describing the resulting state (e.g., what happens if the broadcast is not paused or already complete), which is the only material gap.

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 100%, so all four parameters are already documented, and the description's note about optionally reselecting the agent or caller number largely restates the schema's 'replacement ... if the original is gone' wording. Baseline 3 is appropriate since the description adds little parameter meaning beyond the schema.

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 (resume) and resource (a paused broadcast) and immediately distinguishes the action from its siblings start_broadcast and pause_broadcast by naming the source state (paused). An agent can select this without opening the 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?

Gives a clear precondition (the broadcast must be paused) and an explicit procedural instruction (confirm with the user first). It does not name the sibling tools or say what to do if the broadcast is not paused, but the operative guidance is unambiguous.

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

All Sautikit tools Inspect

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

Need Help?