Sautikit

get_call_recording

Read-only

Check a call recording's availability. Returns {"status":"available","recording_url":...} with a presigned URL (expires in ~15 minutes) once captured; {"status":"pending"} while capture is still in progress (retry shortly); or {"status":"gone"} if it was deleted before capture or the retry budget was exhausted.

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": {
      "call_id": "<call_id>"
    },
    "name": "get_call_recording"
  }
}

Input Schema

Name	Required	Description	Default
`call_id`	Yes	call UUID (or PBX session id starting with HD_)
`purpose`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by enumerating the three possible response states, disclosing that the URL is presigned and expires in ~15 minutes, explaining the pending retry window, and defining exactly when 'gone' occurs (deleted before capture or retry budget exhausted). No contradiction with annotations — this is a read-only check as declared.

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?

A single dense sentence that front-loads the purpose and then walks through each outcome with inline response shapes. The embedded JSON fragments earn their place by making each state unmistakable, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates fully by documenting every return state and the URL expiry, which is exactly the information an agent needs to act on the result. Nothing material for correct invocation is missing.

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% and the schema already documents call_id (UUID or HD_ session id) and the purpose field, so the description adds no parameter-level meaning. Baseline 3 applies since the schema carries that burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check a call recording's availability') and immediately clarifies that the tool is about retrieval/availability rather than call metadata, which cleanly separates it from siblings like get_call, get_call_stats, or list_calls. An agent can pick this tool without opening the schema.

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 rather than spelled out: the agent learns to retry shortly on 'pending', but there is no explicit statement of when to call this versus get_call or when recording retrieval is appropriate (e.g., only after a completed call). The retry hint is the strongest guidance present.

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?