Send Out

Create WhatsApp link

create_whatsapp_link

Read-onlyIdempotent

Makes a WhatsApp click-to-chat (wa.me) link. Use when the user wants to send a WhatsApp message or customer reply. Needs text. phone is optional: with a phone the link opens that chat, without it WhatsApp asks the user to pick a contact. The phone number is reduced to its digits with country code. Opens WhatsApp or WhatsApp Web with the message filled in, and the user presses send. Nothing is sent or stored. Do not use for Instagram, LinkedIn, SMS or bulk email: Send Out cannot send those, so tell the user and offer an email draft instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Message as plain text with line breaks (at most 4,096 characters), such as "Your appointment is confirmed for Tuesday at 3pm."
`phone`	No	Optional recipient phone number with country code, such as +14155552671. Spaces, dashes and brackets are removed; 5 to 15 digits must remain. Leave empty to let the user pick a contact.

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	Yes	Short notes to pass on to the user, including any warning.
`phone`	Yes	Normalized recipient phone digits or null.
`status`	Yes	Always ok when the link was made. Bad input returns an error instead.
`wa_url`	Yes	Official wa.me click-to-chat deep link.
`warning`	No	Warning if URL exceeds safe limits.
`url_length`	Yes	Total length of the generated wa.me URL.
`character_count`	Yes	Length of the message text in characters.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedInput schema / examples

Added value: +[
+  {
+    "phone": "+1 (555) 234-5678",
+    "text": "Your appointment is confirmed for Tuesday at 3pm."
+  }
+]

Changed4 schema fields changedOct 11, 2026

changedInput schema / properties / phone / description

Previous value: -"Optional recipient phone number in international format with country code (for example, +14155552671). Non-digit characters are automatically stripped."New value: +"Optional recipient phone number with country code, such as +14155552671. Spaces, dashes and brackets are removed; 5 to 15 digits must remain. Leave empty to let the user pick a contact."

changedInput schema / properties / text / description

Previous value: -"Message text (at most 4,096 characters). Formatted as plain text with line breaks."New value: +"Message as plain text with line breaks (at most 4,096 characters), such as \"Your appointment is confirmed for Tuesday at 3pm.\""

addedOutput schema / properties / notes / description

Added value: +"Short notes to pass on to the user, including any warning."

addedOutput schema / properties / status / description

Added value: +"Always ok when the link was made. Bad input returns an error instead."

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, so the safety profile is covered. The description still adds real workflow context beyond that: the link opens WhatsApp/WhatsApp Web with the message pre-filled, the human presses send, and 'Nothing is sent or stored' — clarifying the tool itself is non-sending. It does not, however, discuss failure modes or what the generated link response contains.

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?

Front-loaded with the artifact being produced, then usage, then the parameter consequence, then behavior, then exclusions. Every sentence earns its place and none restate the name or title needlessly.

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?

For a 2-parameter, low-complexity link generator with an output schema available, the description covers the artifact produced, both parameters, runtime behavior, and the negative routing case. Nothing an agent needs to select or invoke this correctly is missing, and return values are handled by the output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3. The description goes further by explaining the functional consequence of the optional phone parameter — with it the link opens that specific chat, without it WhatsApp prompts the user to pick a contact — which is behavioral meaning the schema's 'Leave empty to let the user pick a contact' only hints at.

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 opens with a specific verb and artifact: 'Makes a WhatsApp click-to-chat (wa.me) link.' This is instantly distinguishable from siblings like create_x_post, draft_email, or create_calendar_event, since it names the exact output format (wa.me link) rather than a generic 'message' or 'post'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the triggering condition ('Use when the user wants to send a WhatsApp message or customer reply') and explicit exclusions with a fallback ('Do not use for Instagram, LinkedIn, SMS or bulk email... offer an email draft instead'). Both when-to-use and when-not-to-use are spelled out, which is exactly the routing guidance an agent needs among these siblings.

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

All Send Out 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.