Turbo Notify: WhatsApp for AI agents

Send a contact card

send_contact_card

Send a contact card the recipient can save to their phone.

Set exactly one recipient: number, group_id, or contact_id.

phones takes plain E.164 numbers, 1 to 10 of them. emails, organization, title and address are optional extra fields on the card; emails allows up to 10 as well.

A contact card cannot be edited after it is sent: delete_message is the only change for it.

Input Schema

Name	Required	Description	Default
`title`	No	The job title shown on the card, up to 100 characters.
`emails`	No	The email addresses on the card, up to 10.
`number`	No	Recipient phone number in E.164 form, digits only, country code first (e.g. `5511999999999`). Set exactly one of `number`, `group_id` or `contact_id`.
`phones`	Yes	The phone numbers on the card, 1 to 10, each in E.164 form with the country code first (e.g. `5511999999999`).
`address`	No	The postal address on the card, up to 500 characters.
`group_id`	No	Recipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one inbox does not address the same group in another. Set exactly one of `number`, `group_id` or `contact_id`. Addressing a group needs a plan that includes group messaging: without it the call answers `payment_required: feature_not_available`, and retrying will not change that.
`contact_id`	No	Recipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one inbox does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`.
`display_name`	Yes	The name shown on the card, 1 to 200 characters.
`number_alias`	No	Which of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.	main
`organization`	No	The company shown on the card, up to 200 characters.
`idempotency_key`	No	Any printable ASCII text you choose, 1 to 255 characters, for example the id of the event you are answering. Reusing it for the same number suppresses a duplicate if you retry. Without it, retrying after a timeout may deliver the message twice, and the recipient sees both.
`quoted_message_id`	No	Quote an earlier message (`msg_…`) so it appears above yours. Do this only when your text depends on something said a while ago, yours or theirs; do not quote the message you are answering right now, send a normal message instead.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover the safety profile (destructiveHint=false, openWorldHint=true, idempotentHint=false), so the bar is lower. The description adds real behavior beyond them: the card is immutable after sending and delete_message is the only way to remove it, which materially affects an agent's decision to send.

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, front-loaded sentences: purpose, recipient rule, card field constraints, immutability. No filler and every sentence carries actionable information.

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

Completeness4/5

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

An output schema exists so return values need no explanation, and the description covers purpose, recipient exclusivity and post-send immutability. It omits delivery guarantees or plan/permission caveats, though those live in the group_id schema description.

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 every parameter is already documented in detail (E.164 format, limits, idempotency and quoting semantics). The description restates the phones range and optional card fields but adds no syntax or constraint the schema doesn't already carry; 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?

States a specific verb and resource ('Send a contact card') plus the outcome ('the recipient can save to their phone'), which separates it cleanly from send_text, send_media, send_location and send_cta_button in the sibling list.

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 the key selection rule for the recipient parameters ('Set exactly one recipient: number, group_id, or contact_id') and notes deletion as the only follow-up action. It stops short of naming an alternative tool or an explicit when-not-to-use condition, but the context is unambiguous.

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

All Turbo Notify: WhatsApp for AI agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.