Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Draft a WhatsApp location

send_location

Draft a map pin with optional place name and address for preview; it does not send until the user approves, then use confirm_send to share it.

Instructions

Draft a map pin, optionally labelled with a place name and address. Does not send. Show the preview; after the user says yes, call confirm_send.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPlace name shown on the pin
addressNoStreet address shown under the name
chat_idYesChat id as returned by another tool ("<digits>@s.whatsapp.net" or "<id>@g.us"), or a phone number in international format
latitudeYesLatitude in decimal degrees
longitudeYesLongitude in decimal degrees
account_idNoRegistry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.9.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is partially covered. The description adds the non-obvious behavioral fact that this call produces a draft only and never transmits, which is meaningful beyond the annotations. It does not mention auth/account requirements, but the schema's account_id description covers that.

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?

Three short sentences, front-loaded with the core action, followed by the critical 'does not send' caveat and the required next step. No filler.

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 mutation tool with no output schema, the description supplies the workflow context an agent needs: it drafts rather than sends, a preview is shown, and confirm_send completes the action. Nothing essential to correct invocation is missing.

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 every parameter (name, address, chat_id, latitude, longitude, account_id). The description only restates that name/address are optional labels, adding little semantics beyond the structured fields. 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 ('Draft') and resource ('a map pin, optionally labelled with a place name and address'), and explicitly says 'Does not send', which separates it from the send-family siblings (send_media, send_message, confirm_send). An agent can identify the 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 Guidelines5/5

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

Gives an explicit operating procedure: show the preview, wait for user confirmation, then call confirm_send. This names the required follow-up sibling and the condition that triggers it, leaving nothing to inference.

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

Deploy Server

Other Tools