Sautikit

set_whatsapp_recording

Idempotent

Turn recording of a number's WhatsApp calls on or off. This is a SautiKit-side capture toggle, not a Meta one: Meta's native recording is available only on its Cloud/WebRTC calling path, which a BYOC SIP integration cannot use.

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": {
      "number_id": "<number_id>",
      "enabled": "<enabled>"
    },
    "name": "set_whatsapp_recording"
  }
}

Input Schema

Name	Required	Description
`enabled`	Yes	true to turn the toggle on, false to turn it off
`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.
`number_id`	Yes	tenant number 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 establish idempotent=true and destructive=false, so the safety profile is clear. The description adds meaningful context that this is a SautiKit-side capture toggle and explains why Meta-native recording cannot be used on a BYOC SIP integration.

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 tightly written sentences with the core action front-loaded and a useful clarifying sentence that earns its place. No redundant or filler wording.

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 low-complexity toggle with fully described parameters and useful annotations, the description covers the essential behavior and the important Meta-vs-SautiKit distinction. Minor omissions such as permissions or effect on in-progress calls do not significantly hinder correct invocation.

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 number_id and enabled are already documented in the schema. The description adds no extra parameter-level semantics beyond what the schema provides, making the baseline 3 appropriate.

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: turning recording of a number's WhatsApp calls on or off. It also clarifies that this is SautiKit-side rather than Meta-native recording, though it does not name or distinguish sibling tools such as set_whatsapp_transcription.

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 usage is implied by the toggle wording and the note that this is not Meta's native recording. However, it does not explicitly say when to use this versus related settings/transcription tools or list prerequisites.

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?