Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_send_whatsapp_typing

Shows the contact a typing indicator while a reply is composed. Always answers {sent, reason}; a missed indicator is cosmetic.

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": {
      "contact_id": "<contact_id>"
    },
    "name": "desk_send_whatsapp_typing"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNooptional: which of the workspace's WhatsApp numbers
numberNooptional: which of the contact's WhatsApp numbers
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.
contact_idYescontact UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds behavior beyond annotations: it always answers {sent, reason} and a missed indicator is cosmetic, telling the agent failures are non-fatal and need no retry. Annotations only cover destructiveHint=false and openWorldHint=true; the description usefully fills in failure semantics and response shape.

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 short sentences, effect stated first, failure note second. No redundant restatement of the name or schema.

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

Completeness3/5

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

For a simple best-effort signal this covers the essentials and the return shape, but with no output schema and no mention of preconditions (open messaging window, contact/number resolution when multiple numbers exist), an agent still has to infer when the call will silently do nothing.

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 each parameter (from, number, purpose, contact_id) is documented in the schema. The description adds no meaning about contact_id vs. number or how 'from' is chosen, so it sits at the baseline.

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 effect: 'Shows the contact a typing indicator while a reply is composed.' An agent can tell this is a presence/UX signal, not a message send, distinguishing it from send_whatsapp_message and desk_send_message. No explicit sibling naming, so not a 5.

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?

'while a reply is composed' implies the moment to call it, but there is no explicit when-not guidance or mention of pairing with send_whatsapp_message, nor any prerequisite such as an open 24-hour WhatsApp window (a sibling tool desk_get_whatsapp_window exists but is not referenced).

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