Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

add_broadcast_contacts

Append a batch of contacts (strict E.164 phones + template variables) to a broadcast. Returns per-row accepted/rejected. Pass idempotency_key so retries do not duplicate contacts.

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>",
      "contacts": "<contacts>"
    },
    "name": "add_broadcast_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
contactsYesbatch of contacts to append
broadcast_idYesbroadcast UUID
idempotency_keyNoclient-chosen key so a retried batch is not double-appended

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?

Annotations establish openWorldHint=false and destructiveHint=false, and the description reinforces the additive nature ('append') while adding non-obvious behavior: per-row accepted/rejected results implying partial success, plus idempotency semantics for retries. It does not say what happens to rejected rows or whether the batch is atomic, which keeps it below a 5.

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 core action front-loaded, followed by return shape and the retry-safety tip. No filler or redundancy.

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 write tool with no output schema, the definition covers the action, the return shape, and retry behavior. The remaining gap is failure semantics (what causes rejection, atomicity), which is minor but not fully covered.

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 all four parameters, including the nested phone/variables fields, are already documented. The description paraphrases E.164 phones, template variables, and the idempotency key, adding only light reinforcement rather than new meaning. 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?

The description states a specific verb (append) plus resource (contacts) and target (a broadcast), which separates it from create_broadcast and add_dialer_contacts. It stops short of naming a sibling explicitly, so differentiation relies on the 'broadcast' qualifier alone.

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?

It gives one concrete usage instruction ('Pass idempotency_key so retries do not duplicate contacts'), which is genuinely actionable. However, there is no guidance on when to use this versus create_broadcast or add_dialer_contacts, and no stated prerequisites such as the broadcast needing to exist or be in a draft state.

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