Skip to main content
Glama
wsapi-chat

WSAPI WhatsApp MCP Server

by wsapi-chat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

whatsapp_send_contact

Send a WhatsApp contact card by display name or full vCard so recipients can save it to their address book. Returns the message ID.

Instructions

Send a contact card, either from a display name or a full vCard. The recipient can save it to their address book. Not idempotent. Returns the message ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient JID
vcardNoRaw vCard string
replyToNo
mentionsNo
displayNameNoDisplay name (auto-generates vCard)
isForwardedNo
replyToSenderIdNo
ephemeralExpirationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv2.0.0
    • changedInput schema / properties / displayName / description
      Previous value: -"Display name for the contact (alternative to vCard)"New value: +"Display name (auto-generates vCard)"
    • removedInput schema / properties / displayName / optional
      Removed value: -true
    • addedInput schema / properties / ephemeralExpiration
      Added value: +{
+  "enum": [
+    "off",
+    "24h",
+    "7d",
+    "90d"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / isForwarded / description
      Removed value: -"Whether the message should be marked as forwarded"
    • removedInput schema / properties / isForwarded / optional
      Removed value: -true
    • removedInput schema / properties / mentions / description
      Removed value: -"List of phone numbers to mention"
    • removedInput schema / properties / mentions / optional
      Removed value: -true
    • removedInput schema / properties / replyTo / description
      Removed value: -"ID of the message being replied to"
    • removedInput schema / properties / replyTo / optional
      Removed value: -true
    • addedInput schema / properties / replyToSenderId
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / properties / to / description
      Previous value: -"Recipient phone number (with @s.whatsapp.net) or group ID (with @g.us)"New value: +"Recipient JID"
    • removedInput schema / properties / vCard
      Removed value: -{
-  "description": "Raw vCard string (alternative to displayName)",
-  "optional": true,
-  "type": "string"
-}
    • addedInput schema / properties / vcard
      Added value: +{
+  "description": "Raw vCard string",
+  "type": "string"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare idempotentHint=false, readOnlyHint=false and openWorldHint=true, and 'Not idempotent' merely restates one of them. The description does add genuinely new context: the recipient can save the card to their address book, and it returns the message ID (valuable since there is no output schema).

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?

Three short, front-loaded sentences with no filler; the only slightly redundant line is 'Not idempotent,' which the annotations already state.

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

Completeness3/5

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

For an 8-parameter mutation tool with low schema coverage and no output schema, the description covers the return value and idempotency but leaves most optional parameters unexplained, so an agent cannot fully understand the call surface.

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 only 38% across 8 parameters, so the description must compensate more than it does. It covers the displayName-vs-vcard choice (implying mutual exclusivity), but replyTo, mentions, isForwarded, replyToSenderId and ephemeralExpiration receive no explanation anywhere.

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?

Names a specific verb (send) and resource (contact card) and the two input modes (display name or full vCard). This clearly separates it from the other whatsapp_send_* siblings (text, image, audio, location, etc.), though it never references those siblings by name.

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?

The phrase 'either from a display name or a full vCard' implicitly tells the agent the two ways to call it, but there is no explicit when-to-use rule, prerequisite, or exclusion versus alternatives like whatsapp_create_contact or whatsapp_send_text with a link.

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