Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

send_whatsapp_call_button

Send an interactive message with a tap-to-call button, letting the contact start a WhatsApp call to you in one tap — the inbound counterpart to request_whatsapp_call_permission. display_text and ttl_minutes fall back to Meta's defaults ("Call Now", 7 days) when omitted.

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": {
      "to": "<to>",
      "text": "<text>"
    },
    "name": "send_whatsapp_call_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesrecipient WhatsApp id (a phone number)
textYesbody text shown above the call button
payloadNoopaque value echoed back to you when the contact taps the button
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.
number_idNoSautikit number id (a UUID from list_numbers) to send from — NOT Meta's phone_number_id; Sautikit maps it to Meta's id by matching the number E.164 against connected WhatsApp accounts. Mutually exclusive with connection_id
ttl_minutesNohow long the button stays tappable; Meta defaults to 10080 (7 days)
display_textNobutton label; Meta defaults it to "Call Now" when omitted
connection_idNoUUID of the WhatsApp connection to send from; mutually exclusive with number_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare non-destructive and closed-world behavior, so the bar is lower. The description adds useful context that omitted fields fall back to Meta defaults and that the button is temporarily tappable, but it does not describe what the send returns or failure modes such as an invalid recipient or expired calling window.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core action and the sibling relationship front-loaded; the default-values note at the end is short and earns its place. The em-dash aside is dense but readable.

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 8-parameter messaging tool with no output schema, the definition covers action, direction, and default behavior adequately. The main gap is response behavior (what identifier or acknowledgment comes back), which the agent would have to infer.

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 the schema already documents every parameter including the mutual exclusivity of number_id and connection_id. The description only restates the defaults for display_text and ttl_minutes that the schema itself already specifies, adding no new meaning.

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 ('Send an interactive message with a tap-to-call button') and clarifies the direction of the call (contact calls you), which distinguishes it from outbound calling siblings.

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?

Positions itself explicitly as 'the inbound counterpart to request_whatsapp_call_permission', giving the agent a clear routing rule between the two call-flow tools. It stops short of stating when not to use it or naming the plain-text alternative (send_whatsapp_message).

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