Skip to main content
Glama

Hand over to WhatsApp

get_whatsapp_handoff
Read-only

Generate a pre-filled WhatsApp deep link to hand the customer off to the right contact. Garden Route locations (Knysna, Plett, George, Sedgefield, etc.) route to Duncan Kane on WhatsApp (+27795235407) for a free in-home consultation; all other South African locations route to the shop WhatsApp (+27760228410), WhatsApp only, no voice calls. Use when the customer prefers human assistance or when self-serve checkout isn't appropriate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_whatsapp_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoOptional additional message to prefill
locationNoCity/suburb. Drives Duncan vs shop routing.
customer_nameNo
product_contextNoe.g. 'roller blockout for bedroom'

Output Schema

NameRequiredDescriptionDefault
reasonYes
recipientYes
whatsapp_urlYes
recipient_phoneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the two routing destinations with phone numbers, the geographic split, and the constraint 'WhatsApp only, no voice calls' — a channel limitation the agent could not infer otherwise.

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?

Front-loaded with the action and outcome, then routing detail, then usage condition. Dense but every clause carries information; the parenthetical town list is slightly verbose but justifies the routing boundary.

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-value explanation is unnecessary, and the description covers routing, channel constraints, and usage triggers. Only minor gap is whether the link is returned as a URL string versus opened directly, which the output schema presumably resolves.

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 75%, and the description adds the actual routing rule (Garden Route towns → Duncan Kane, all other SA locations → shop number) that the schema only alludes to with 'Drives Duncan vs shop routing.' It also frames message as optional prefill, reinforcing the schema.

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 artifact ('Generate a pre-filled WhatsApp deep link') plus the goal ('hand the customer off to the right contact'). The routing rules make it unmistakable versus any sibling tool, none of which deal with WhatsApp handoff.

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 explicit trigger conditions: 'Use when the customer prefers human assistance or when self-serve checkout isn't appropriate.' It does not name a specific alternative tool to prefer, but the conditions are clear enough to select correctly.

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.

Resources