Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Send a map location

send_location

Send a WhatsApp 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "send_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA link shown beside the pin.
nameNoA name for the place, up to 200 characters.
numberNoRecipient phone number in E.164 form, digits only, country code first (e.g. `5511999999999`). Set exactly one of `number`, `group_id` or `contact_id`.
addressNoThe place's address, up to 500 characters.
group_idNoRecipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one number 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.
latitudeYesLatitude, between -90 and 90.
longitudeYesLongitude, between -180 and 180.
contact_idNoRecipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one number does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`.
number_aliasNoWhich 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_keyNoAny 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, but only for the same request: the same key with another recipient or another text is refused as idempotency_key_conflict and nothing is sent, so use a new key for each new message. Without it, retrying after a timeout may deliver the message twice, and the recipient sees both.
quoted_message_idNoQuote 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / contact_id / description
      Previous value: -"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`."New value: +"Recipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one number does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`."
    • changedInput schema / properties / group_id / description
      Previous value: -"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."New value: +"Recipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one number 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."
  2. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"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."New value: +"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, but only for the same request: the same key with another recipient or another text is refused as idempotency_key_conflict and nothing is sent, so use a new key for each new message. Without it, retrying after a timeout may deliver the message twice, and the recipient sees both."
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare destructiveHint=false and idempotentHint=false, and the description adds genuinely useful context beyond them: a sent location is immutable and delete_message is the sole corrective action. That is a real behavioral disclosure an agent could not infer from the annotations. It omits permission or rate-limit behavior, which keeps it below a 5.

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 short and front-loaded, leading with the action before constraints, and the paragraph breaks make the recipient rule and immutability note scannable. The coordinate range sentence duplicates schema constraints verbatim, which is the one piece of avoidable repetition.

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, open-world send tool with a full schema and an output schema, the description covers the essentials: what is sent, how the recipient is chosen, and that the result cannot be edited. Idempotency, number selection, and quoting are left entirely to their schema descriptions, which is acceptable given 100% coverage and a declared return schema.

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 latitude/longitude ranges, name/address/url roles, recipient exclusivity, and number_alias. The description largely restates those same facts (coordinate bounds, label fields, one-recipient rule) without adding syntax, format, or interaction detail. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opening sentence states a specific verb and resource ('Send a WhatsApp location pin'), which is immediately distinguishable from siblings like send_text or send_media. It does not explicitly name the alternative senders, so sibling differentiation is implied by the resource type rather than stated.

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 gives one hard usage rule — 'Set exactly one recipient' across number, group_id, or contact_id — and points to delete_message as the only remedy after sending. It offers no guidance on when to send a location instead of a text or media message, so the when-to-use dimension is only implied by the tool's purpose.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.