Chatway Live Chat

Request Human Handoff

handoff-to-human

Request human-agent handoff for a Chatway conversation that is currently handled by a Chatway AI assistant. Returns an error if no AI assistant is assigned to the conversation; in that case, assign a teammate with assign-conversation or add a private note instead. This records a handoff request but does not guarantee that a human has joined or replied. Use it when the customer asks for a person or the request cannot be handled with the available tools; after handoff, do not reply with send-message.

Input Schema

Name	Required	Description	Default
`conversation_id`	Yes	UUID of the conversation that needs a human agent.

Output Schema

Name	Required	Description	Default
`status`	No
`conversation_id`	No	Conversation UUID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / conversation_id / description

Added value: +"UUID of the conversation that needs a human agent."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "conversation_id": {
+      "description": "Conversation UUID.",
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "handoff_requested"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Adds substantive behavior beyond the annotations: it records a request but does not guarantee a human has joined or replied, it errors when no AI assistant is assigned, and it constrains follow-up messaging. None of this is derivable from readOnlyHint=false / destructiveHint=false / 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?

Front-loaded with the action and its precondition, and every sentence carries usable information. Slightly repetitive in restating 'Chatway AI assistant' and could tighten the clause about erroring into a shorter form.

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?

A one-parameter mutation tool with an output schema and rich annotations; the description covers the precondition, failure mode, non-guarantee, and follow-up restriction. Nothing an agent needs to invoke it correctly 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 100% and documents conversation_id as a UUID, so the schema carries the type burden. The description still adds meaning by constraining which conversation is valid (one currently handled by an AI assistant) and what happens if that constraint is violated.

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 resource: 'Request human-agent handoff for a Chatway conversation that is currently handled by a Chatway AI assistant.' The precondition (AI assistant must be assigned) distinguishes it from the similarly named assign-conversation and resolve-conversation siblings.

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 the trigger condition ('when the customer asks for a person or the request cannot be handled with the available tools'), names the fallback alternatives when the precondition fails ('assign a teammate with assign-conversation or add a private note instead'), and states a post-condition rule ('after handoff, do not reply with send-message').

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

All Chatway Live Chat 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.

Resources

Need Help?