Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

list_broadcasts

Read-only

List AI voice broadcasts with per-row funnel rollup (total/queued/attempted/reached) and spend. Filter by state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_broadcasts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNopage size
stateNofilter: draft, running, paused, completed
cursorNopagination cursor
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description's added value is the return shape: each row carries a funnel rollup and spend, which is real behavioral context a caller could not get from annotations. It omits any note about pagination semantics for limit/cursor, which is the remaining gap.

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 tight sentences: the resource and returned data come first, the filter control second. No filler, no restatement of the tool name, nothing that could be cut without losing 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?

With no output schema, the description usefully summarizes the returned fields, which is the main thing an agent needs for a list tool. Pagination behavior (how cursor interacts with limit, whether an end cursor is returned) is the only meaningful omission.

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 description coverage is 100%, so limit, state, cursor and purpose are already documented, including the enumerated state values. The description's "Filter by state" adds nothing the schema does not already say, and it does not explain the per-call purpose requirement. Baseline 3 applies.

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?

States a specific verb and resource ("List AI voice broadcasts") plus the distinguishing payload (funnel rollup total/queued/attempted/reached and spend). It never names the nearest siblings (get_broadcast, get_broadcast_report, list_dialer_campaigns), so the agent must infer the boundary itself.

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?

"Filter by state" implies the intended use case, but there is no explicit when-to-use or when-not-to-use guidance. In particular, nothing tells the agent to prefer this over get_broadcast_report for spend reporting or over list_dialer_campaigns for dialer campaigns.

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