Sautikit

list_calls

Read-only

List the workspace's calls, newest first. Filter by direction, status, date range, phone substring, or broadcast/contact. Paginate with cursor + limit; the response carries next_cursor.

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": {
      "purpose": "<purpose>"
    },
    "name": "list_calls"
  }
}

Input Schema

Name	Required	Description
`q`	No	phone-number substring search
`to`	No	end bound: RFC3339, YYYY-MM-DD, or unix seconds
`from`	No	start bound: RFC3339, YYYY-MM-DD, or unix seconds
`limit`	No	page size (server default when omitted)
`cursor`	No	pagination cursor from a previous page's next_cursor
`status`	No	comma-separated status filter, e.g. completed,failed,no_answer,busy
`purpose`	Yes	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.
`direction`	No	filter by direction: outbound or inbound
`contact_id`	No	only calls for this broadcast contact (UUID)
`session_id`	No	only the call matching this exact PBX session id (starts with HD_)
`broadcast_id`	No	only calls belonging to this broadcast (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new behavior: default sort order (newest first) and the pagination contract where the response carries next_cursor. It does not mention the server-default page size or any bounds on limit, which would have completed the picture.

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 sentences, front-loaded with the resource and scope, then filters, then pagination. No redundant restatement of the name or title and no filler.

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 an 11-parameter read tool with full schema coverage and no output schema, the description covers scope, filtering, ordering, and the pagination loop sufficiently to call it correctly. Minor gaps remain around default page size and where session_id filtering fits in the filter list.

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 the schema already documents every parameter including cursor semantics and accepted date formats. The description groups the filters into recognizable categories and confirms the cursor/next_cursor loop, but adds no syntax or constraint detail beyond the schema.

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 the workspace's calls') plus a default ordering ('newest first'), which distinguishes it from get_call and get_call_stats. It stops short of explicitly naming the sibling to use for a single call or for aggregates.

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 only implied: the enumeration of filters tells the agent what it can narrow by, but there is no statement of when to prefer this over get_call, get_call_stats, or list_dialer_attempts, and no 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 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?