Whatify MCP Server

whatify_send_message

Send a free-form WhatsApp text message to a phone number. Provide recipient phone number and message body; optionally select a connected WhatsApp account.

Instructions

Send a free-form WhatsApp text message to a phone number via Whatify.

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": {
      "phone": "<phone>",
      "message": "<message>"
    },
    "name": "whatify_send_message"
  }
}

Input Schema

Name	Required	Description
`phone`	Yes	Recipient phone number, with or without country code
`message`	Yes	Text message body
`whatsapp_account_id`	No	Specific connected WhatsApp account id; defaults to the first connected account

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 14, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description bears full burden. It only mentions 'free-form' and repeats schema constraints, failing to disclose rate limits, delivery guarantees, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with key action and resource; no excess words, though could incorporate more context.

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

Completeness2/5

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

Absent output schema and annotations, the description omits important context like return value, error handling, and account identification behavior, leaving the agent underinformed.

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 baseline is 3; description adds no new meaning beyond schema descriptions (e.g., 'free-form' is not tied to a parameter).

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?

The description uses specific verb 'Send' and resource 'free-form WhatsApp text message', clearly differentiating from siblings like whatify_send_template and whatify_send_flow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as whatify_send_template or whatify_send_flow, leaving the agent without context for selection.

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

Deploy Server