Skip to main content
Glama
wsapi-chat

WSAPI WhatsApp MCP Server

by wsapi-chat
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

whatsapp_send_contact

Send contact information as a vCard message to a WhatsApp recipient, specifying either a display name for automatic vCard generation or a custom vCard string.

Instructions

Send a contact (vCard) message. Provide either displayName or vcard.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  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

C2.7/5.0
Behavior1/5

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

No annotations are provided, so the description must carry the full behavioral burden, but it fails to disclose any behavioral traits such as what happens if both displayName and vcard are provided, validation of vcard format, or the nature of the message delivery.

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?

The description is very short and front-loaded, conveying the core purpose in one sentence. While it could benefit from more structure, it is efficient and avoids unnecessary words.

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?

Given 8 parameters, no output schema, and no annotations, the description leaves major gaps. It does not explain the 'to' parameter format (JID), the behavior of optional parameters, or the return value, making it incomplete for safe usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 38% schema coverage, the description adds minimal value by mentioning displayName and vcard as alternatives. It does not explain the format required for vcard, the meaning of other parameters like mentions or replyTo, or confirm if displayName or vcard is needed beyond the mutual exclusivity hint.

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?

The description clearly states it sends a contact (vCard) message, which distinguishes it from other send_* tools like send_text or send_image. However, it does not explicitly differentiate from the similar-sounding 'whatsapp_create_contact' 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?

It provides a usage hint to 'provide either displayName or vcard', implying mutual exclusivity, but lacks explicit guidance on when to use this tool versus alternatives like send_text or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wsapi-chat/wsapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server