Skip to main content
Glama
WhatsApp MCP Server

WhatsApp MCP Server

send_message

Sends a WhatsApp message to a phone number or JID through the native desktop app after explicit confirmation and OS biometric verification.

Instructions

Send a WhatsApp message to a phone number or JID. Requires explicit user confirmation (confirm=true) and native OS biometric verification (Touch ID / Windows Hello). Dispatches message using the native desktop WhatsApp application.

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>",
      "text": "<text>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesMessage content to send.
confirmNoExplicit confirmation to execute this write operation. Must be set to true.
recipientYesTarget phone number (e.g. '+31612345678' or '31612345678') or WhatsApp JID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does a good job stating the confirmation and biometric requirements plus the native desktop dispatch behavior. It omits whether sending is irreversible and what happens on failure, preventing a top score.

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 compact sentences, front-loaded with the action, followed by safety prerequisites and dispatch mechanism. Every sentence adds useful information with no wasted wording.

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?

Complete enough for a three-parameter mutation tool: it identifies the action, target, and mandatory confirmation/biometric checks. Some outcome or error context is absent, but the lack of an output schema and the strong schema coverage reduce that gap.

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 input schema already documents recipient formats, text, and confirm. The description reinforces the confirm=true requirement but adds little parameter meaning beyond what the schema provides, making the baseline 3 appropriate.

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 action and resource: send a WhatsApp message to a phone number or JID using the native desktop app. This is clear and distinct from generic messaging tools, though it does not explicitly distinguish itself from the sibling draft_message tool.

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?

Provides important prerequisites: explicit confirmation via confirm=true and native OS biometric verification. However, it does not explain when to use this tool rather than draft_message, nor does it describe failure cases or when sending should be avoided.

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