Sautikit

rotate_whatsapp_trunk

Re-mint the SIP credentials behind a number's WhatsApp trunk without disconnecting the WhatsApp account or changing the bound phone_number_id. Asynchronous — poll get_whatsapp_calling.

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>"
    },
    "name": "rotate_whatsapp_trunk"
  }
}

Input Schema

Name	Required	Description	Default
`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 (from list_numbers) — NOT the trunk id

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations, the description discloses important behavior: the operation is asynchronous and preserves the WhatsApp account and phone_number_id binding. It does not state whether old SIP credentials are immediately invalidated or what failure behavior looks like, but it adds meaningful context for a mutation tool.

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?

The description is two sentences, front-loaded with the action and its key non-effects, then ends with the asynchronous follow-up instruction. There is no unnecessary 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 an asynchronous mutation tool with no output schema, the description provides the essential completion path by naming get_whatsapp_calling. It is nearly complete, though it does not explain how to confirm success or what state the rotated credentials will be in.

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 parameter meanings are already documented in the input schema. The description refers to a number's trunk but does not add syntax or clarify number_id versus trunk id beyond what the schema provides, so the baseline is appropriate.

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?

The description states a specific verb and resource: re-mint the SIP credentials behind a number's WhatsApp trunk. It also clarifies the scope by saying the WhatsApp account is not disconnected and the bound phone_number_id is unchanged, which distinguishes this from broader SIP credential rotation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear operational guidance by noting the action is asynchronous and directing the agent to poll get_whatsapp_calling. It does not explicitly compare this tool with rotate_sip_credential or explain when rotation is warranted, so it stops short of full alternative routing.

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?