Skip to main content
Glama

Send WhatsApp text

whatsapp_send_text
Destructive

Sends a free-text WhatsApp message to one recipient. Free text is accepted only inside an open 24-hour customer session; outside it, only an approved template can be sent. With dryRun: true it returns the message that would be sent, without sending.

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

Input Schema

NameRequiredDescriptionDefault
toYesRecipient in international format, e.g. +919876543210
textYesMessage body
dryRunNoIf true, validate and return the payload without sending

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the description's main job is context — and it delivers the non-obvious 24-hour session window, which is the key failure mode for this call. It also clarifies dryRun's no-side-effect behavior. It stops short of saying what happens on a session-window violation (error vs. silent rejection) or any rate-limit behavior.

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?

Three sentences, front-loaded with the action, then the gating constraint, then the dry-run escape hatch. No filler and nothing repeated from structured fields.

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 destructive, open-world send tool with no output schema, the description covers the two things an agent must know: the session-window restriction and the dryRun safety valve. It omits the failure behavior outside the window and any indication of what a successful send returns (e.g. a message id for later whatsapp_message_status lookup).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it constrains the `text` parameter to session-scoped free text and clarifies that dryRun returns the would-be payload without delivering it. It adds nothing about the `to` format beyond the schema's own example.

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 ("Sends a free-text WhatsApp message") plus scope ("to one recipient"). The word "free-text" immediately distinguishes it from whatsapp_send_template, so an agent can route correctly without opening either schema.

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?

Gives an explicit precondition: free text works only inside an open 24-hour customer session, and outside it only an approved template can be sent. That effectively states when-not-to-use and points at the template path, though it never names whatsapp_send_template explicitly as the fallback.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.