Skip to main content
Glama

Pass the customer to a person

hand_off_to_team

Passes the customer, with a short summary of what they need, to a person on the business’s team, who contacts them on WhatsApp or by phone. For when the customer asks for a person. Only for businesses that take requests through AI assistants; others answer with their WhatsApp and chat links.

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": {
      "business": "<business>",
      "phone": "<phone>",
      "summary": "<summary>"
    },
    "name": "hand_off_to_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
phoneYesThe customer’s phone or WhatsApp number with country code, e.g. +91 98765 43210, shared by the customer to be contacted.
summaryYesWhat the customer needs, in a few sentences.
businessYesThe business id from find_businesses, e.g. "carat-story".

Output Schema

NameRequiredDescriptionDefault
idNo
statusYes
next_stepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations mark this as a non-read-only, non-destructive, non-idempotent call, and the description adds real context beyond them: the handoff routes to a human who makes outbound contact on WhatsApp or phone, and it is gated on the business accepting AI-submitted requests. It does not say what occurs on failure or whether duplicate handoffs are possible, which matters given idempotentHint=false.

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?

Three short sentences with the core action front-loaded and the eligibility caveat last, which is the right order. The fragment 'For when the customer asks for a person.' is slightly clipped but still readable, and nothing is redundant.

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 four-parameter mutation with an output schema and full annotation coverage, the description supplies the routing behavior, the trigger condition, and the eligibility gate an agent needs to decide whether to call it. Return values are covered by the output schema, so nothing essential is missing.

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%, so the description needs to add some meaning, and it does: 'contacted on WhatsApp or by phone' clarifies the intent of the phone field and 'a short summary of what they need' frames the summary field. The business and name parameters are left entirely to the schema, which does document the business id reference.

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 description states a specific action and object: passing the customer with a summary to a person on the business's team who then contacts them via WhatsApp or phone. That is concrete and distinguishable from data-lookup siblings like get_business or search_products. It does not explicitly contrast with the closest sibling, create_lead, so it falls short of a 5.

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?

It gives a clear trigger ('For when the customer asks for a person') and a precondition ('Only for businesses that take requests through AI assistants'), plus what to do otherwise (answer with WhatsApp and chat links). That is strong when-to-use guidance, but it never names an alternative tool for the non-AI-business case or for non-human-handoff requests.

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