Skip to main content
Glama
rukman7

whatsapp-mcp-server

by rukman7

Send WhatsApp Contact

whatsapp_send_contact

Send a contact card to a WhatsApp user with name, phone, and optional email. Specify the recipient's number and contact details.

Instructions

Send a contact card to a WhatsApp user.

Args:

  • to (string): Recipient phone number

  • first_name (string): Contact first name

  • last_name (string, optional): Contact last name

  • phone (string): Contact phone number

  • email (string, optional): Contact email

Returns: Message ID and delivery status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient phone number in international format (e.g. '353851234567' or '+353851234567')
emailNoContact's email address
phoneYesContact's phone number
last_nameNoContact's last name
first_nameYesContact's first name
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior3/5

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

Annotations indicate readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the agent knows it is a side-effecting operation. The description adds the return value ('Message ID and delivery status') but does not disclose other behavioral traits like authentication needs, rate limits, or failure conditions. No contradiction with annotations.

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 structured as a one-sentence summary followed by a clear args list and a returns note. It is concise and easy to scan, though it somewhat duplicates schema information. No unnecessary fluff is present.

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?

With 6 parameters and no output schema, the description provides return value information but lacks usage differentiation, error scenarios, or prerequisites. The missing 'response_format' parameter guidance also leaves a gap. Overall, it is adequate for a simple send tool but not comprehensive.

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?

The schema provides full descriptions for all 6 parameters (100% coverage), so the baseline is 3. The description repeats some parameter details but omits the 'response_format' parameter entirely, and it does not add meaningful semantic value beyond the schema. The schema already explains format and constraints.

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 clearly states 'Send a contact card to a WhatsApp user', specifying the verb (send) and resource (contact card). This distinguishes it from sibling tools like whatsapp_send_text or whatsapp_send_image, which serve different content types. The purpose is immediately obvious.

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 description implies usage for sending contact cards, but it does not explicitly state when to use this tool versus alternatives. There is no mention of exclusions or comparison to sibling send tools. The intended use is apparent from the title and name, but not explicitly guided.

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/rukman7/whatsapp-mcp-server'

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