Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

list_dialer_contacts

Read-only

List a campaign's contacts with their status and attempt counts; filter by status. On a campaign with retry.ordering best_time each contact also carries best_hour, its most likely local answer hour.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "list_dialer_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNopage size, 1 to 200
cursorNopagination cursor
statusNofilter: queued, calling, connected, waiting_retry, completed, exhausted, suppressed, canceled, callback
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.
campaign_idYescampaign UUID

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 already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's job is to add context — and it does, disclosing that each contact carries status and attempt counts and that best_hour appears conditionally only when retry.ordering is best_time. That conditional-field disclosure is genuinely useful behavior an agent could not infer from annotations or schema.

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 compact sentences with the core capability front-loaded and the conditional output caveat second. No filler, no restatement of the tool name.

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 names the returned fields (status, attempt counts, best_hour) rather than leaving return shape opaque. Pagination and the purpose parameter are left entirely to the schema, which is adequate given 100% coverage, but a brief note on paging expectation would close the remaining 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 limit, cursor, status enum values, campaign_id, and the purpose requirement are all fully documented in the schema. The description only echoes the status filter and adds no syntax or semantics beyond it, so the baseline of 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 a campaign's contacts') plus what is returned ('status and attempt counts') and the available filter. It is clearly distinct from list_dialer_attempts by scoping to contacts rather than attempts, though it never names that sibling to make the distinction explicit.

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?

Usage is implied by 'a campaign's contacts ... filter by status', giving the agent enough to know it is the per-campaign contact roster. There is no explicit when-to-use vs list_dialer_attempts, get_dialer_live, or get_dialer_report, and no stated prerequisites or exclusions.

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