Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

add_dialer_suppression

Idempotent

Add a number to the workspace suppression list: no campaign will ever dial it (optionally until expires_at).

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": {
      "phone": "<phone>"
    },
    "name": "add_dialer_suppression"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesE.164 number that must never be dialed by any campaign
reasonNowhy (max 500 characters)
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.
expires_atNoRFC 3339 time in the future; omit for permanent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the durable, workspace-wide effect of the entry, but it omits what happens on duplicate submission, whether an existing suppression can be removed, and any permission requirements.

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

Conciseness4/5

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

A single sentence that front-loads the action and follows immediately with the consequence. No filler, though the parenthetical about expires_at is slightly awkwardly placed at the end.

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 simple four-parameter create tool with full schema coverage, annotations, and no output schema, the description covers the essentials: what it adds, the scope (workspace), and the permanence option. It falls short only on duplicate handling and reversal, which an agent running a suppression workflow might reasonably need.

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 phone, reason, purpose, and expires_at are all documented in the schema already. The description's mention of "optionally until expires_at" restates the schema's "omit for permanent" without adding new format or constraint detail, so 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 names a specific verb and resource ("Add a number to the workspace suppression list") and states the concrete consequence ("no campaign will ever dial it"). That effect cleanly distinguishes it from contact-adding siblings such as add_dialer_contacts, though no sibling is named explicitly.

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 context of use is implied by the suppression effect and the optional expires_at, so an agent can infer this is a do-not-call tool. However, there is no explicit when-to-use guidance, no mention of when to prefer permanent vs. expiring suppression, and no pointer to any alternative or follow-up tool.

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