Skip to main content
Glama
Sign In
askmywa

askmywa

by Ruwad-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Send a text message

send_message
Destructive

Send WhatsApp text messages to a person or group by previewing the recipient and content first, then sending only after explicit approval.

Instructions

Send a WhatsApp text message to a person or a group.

Safety: with confirm=false (the default) NOTHING is sent; the tool returns a preview (resolved recipient, their name, whether it is a group, the text). Show it to the user and call again with confirm=true only after they approved that exact content. Never set confirm=true on the first call. Recipient: phone number with country code and no plus sign, a JID (123@s.whatsapp.net, 123@g.us for a group) or a contact name.

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": {
      "recipient": "<recipient>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNofalse (default) only previews; true sends, after the user approved the preview
messageYestext to send
recipientYesphone number with country code (no +), a JID (x@s.whatsapp.net or x@g.us) or a contact name

Output Schema

NameRequiredDescriptionDefault
sentYestrue only when the message left the account
messageYeshuman-readable status
previewNo
timestampNoserver timestamp of the sent message
message_idNo
needs_confirmationYestrue when this was a preview: repeat the call with confirm=true after the user approved

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say destructiveHint=true and non-idempotent; the description adds the crucial behaviour that the default call is a dry run that sends nothing and instead returns resolved recipient, their name, group flag and text. That preview contract and the approval gate are exactly the kind of context annotations cannot express.

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 front-loaded sentences with a labelled 'Safety:' segment placed before the recipient formatting details. Every sentence carries operational information; nothing is redundant.

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

Completeness5/5

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

An output schema exists so return values need not be spelled out, yet the description still names the preview fields an agent must surface. Safety annotations plus the confirm workflow fully cover what an agent needs to call this mutation correctly.

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 all three parameters are already documented, including confirm's preview/send semantics. The description largely restates the recipient formats (phone, JID, contact name) rather than adding syntax or edge-case detail beyond the schema.

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 a WhatsApp text message') plus the target scope ('to a person or a group'). The word 'text' plus the recipient-format guidance distinguish it from the send_audio_message and send_file siblings without needing their schemas.

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 a precise when-and-how: call with confirm=false, show the preview, then re-call with confirm=true only after explicit approval, and 'Never set confirm=true on the first call.' It does not explicitly route to siblings (e.g. 'for attachments use send_file'), so it stops short of full when-not guidance.

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

Deploy Server

Other Tools