Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

get_whatsapp_call_settings

Read-only

Read a number's WhatsApp call settings: what SautiKit last persisted ("stored") plus a best-effort live read from Meta ("live") and any Meta-imposed "restrictions". A failed live read still returns 200 with "stored" and a "live_error" — treat stored as authoritative and live as a bonus.

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": "get_whatsapp_call_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
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_idYestenant number UUID (from list_numbers) — NOT the trunk id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, so safety is covered; the description adds genuinely non-obvious behavior: a dual-source read, a best-effort Meta call that can fail, and a still-200 response with a "live_error" field. This partial-failure semantics is exactly the kind of thing an agent cannot infer from structured fields, though auth or rate-limit caveats for the Meta call are not mentioned.

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 what is read and immediately followed by the fallback rule. Every clause carries information; the fallback behavior is stated before any question about it could arise.

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?

With no output schema, the description correctly takes on the job of naming the returned keys ("stored", "live", "restrictions", "live_error") and their precedence, which makes the tool callable. The remaining gap is sibling disambiguation against get_whatsapp_calling, which leaves the agent guessing at the margin.

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%, and the schema already explains that number_id is the tenant number UUID (not the trunk id) and that purpose is required for read tools. The description adds no parameter-level meaning beyond "a number's ... settings", so the baseline 3 applies.

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?

"Read a number's WhatsApp call settings" gives a specific verb and resource, and the description goes on to enumerate the exact fields returned ("stored", "live", "restrictions"). It stops short of distinguishing this from the sibling get_whatsapp_calling / get_whatsapp_call_permission, so an agent must infer the boundary.

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?

There is strong guidance on how to interpret results ("treat stored as authoritative and live as a bonus"), but no explicit statement of when to call this versus get_whatsapp_calling or update_whatsapp_call_settings, and no prerequisites such as whether WhatsApp calling must already be enabled.

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