Turbo Notify: WhatsApp for AI agents

Send a map location

send_location

Send a location pin.

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

latitude is between -90 and 90, longitude between -180 and 180. name and address label the pin; url adds a link beside it.

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

Input Schema

Name	Required	Description	Default
`url`	No	A link shown beside the pin.
`name`	No	A name for the place, up to 200 characters.
`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`.
`address`	No	The place's address, 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.
`latitude`	Yes	Latitude, between -90 and 90.
`longitude`	Yes	Longitude, between -180 and 180.
`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`.
`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
`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?

Beyond the annotations, the description discloses the critical behavior that a sent location is immutable and that delete_message is the only corrective action, which an agent needs before committing. The group plan gate (`payment_required: feature_not_available`) and the retry-duplication behavior of idempotency_key live only in the schema, so the description leaves some operational context uncovered.

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 a one-line purpose, then grouped into recipient rule, coordinate bounds, labeling fields, and immutability. Every line carries a distinct constraint and there is no filler.

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?

For an 11-parameter outbound-send tool with a full schema and an output schema, the description covers the highest-risk facts: destination selection and irreversibility. It omits the number_alias channel selector and the idempotency retry story, both of which are documented in the schema, so the gap is minor.

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 100%, so the schema already documents recipient exclusivity, lat/long bounds, name/address limits, number_alias, and idempotency_key. The description restates the exactly-one-recipient rule and coordinate ranges without adding syntax or examples, so it meets the baseline rather than exceeding it.

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?

"Send a location pin" states a specific verb and resource, and the resource is clearly distinct from the neighboring send_* tools (send_text, send_media, send_contact_card, send_cta_button). An agent can select this tool without opening the schema.

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?

The description gives the key selection constraint (exactly one of number, group_id, contact_id) and points to delete_message as the only remedy after sending, which routes the agent correctly on follow-up actions. It does not explicitly contrast with text/media sending, but the resource distinction makes that implicit.

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.