Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Draft a WhatsApp text message

send_message

Draft a WhatsApp text message and show a preview before sending. Returns a draft ID and recipient/text preview; call confirm_send after user approval.

Instructions

Draft a text message. Does not send. Returns a draft_id and a preview of the recipient and exact text. Show that preview to the user; after they say yes, call confirm_send. A draft lasts 15 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe message text
chat_idYesChat id as returned by another tool ("<digits>@s.whatsapp.net" or "<id>@g.us"), or a phone number in international format
reply_toNoQuote-reply to this message
account_idNoRegistry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.
mention_idsNoChat ids to @-mention; include their names in the text yourself

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.9.3

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the call does not send, it returns a draft_id and a recipient/text preview, and the draft expires in 15 minutes. The annotations only declare non-readOnly, non-destructive and non-idempotent; the description supplies the stateful draft lifecycle and the required user-confirmation step that drive correct usage.

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?

Four short sentences, front-loaded with the most important fact (it drafts, it does not send), then return values, then the required next step, then the expiry. Every sentence carries load with no filler.

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?

No output schema exists, but the description compensates by naming the return value (draft_id plus preview) and the mandatory confirm_send step, plus the 15-minute validity window. For a stateful two-step mutation flow, this is sufficient for an agent to call it 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 the schema already documents chat_id, text, reply_to, account_id and mention_ids in detail. The description adds no parameter-level syntax or defaults, so the baseline 3 applies.

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 name 'send_message' implies a send, but the description immediately corrects this with 'Draft a text message. Does not send.' — a specific verb+resource combined with a scope correction that an agent cannot infer from the name alone. It also names the follow-up sibling confirm_send, distinguishing this from the tool that actually sends.

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 clear workflow guidance: show the preview to the user, and after approval call confirm_send. This tells the agent when to escalate to the sibling. It stops short of stating when to prefer send_media/send_poll/send_location for non-text payloads, so it is strong but not fully exhaustive.

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