Chatway Live Chat

Unresolve Conversation

unresolve-conversation

Reopen one or more resolved Chatway conversations. Send all target conversation UUIDs in one call and obtain user confirmation before changing their status. Use resolve-conversation to close them again.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`conversation_ids`	Yes	Conversation UUIDs to reopen, from 1 to 100.
`confirmation_token`	No	Required after the confirmation challenge. Ask the user to approve before calling again with this token.

Output Schema

TableJSON Schema

Name	Required	Description
`queued`	No	True when several conversations were queued as background jobs.
`message`	No	Message describing the action or its result.
`affected_count`	No	Number of records the action will change.
`confirmation_token`	No	Pass back as confirmation_token after the user approves.
`expires_in_seconds`	No	How long the confirmation token stays valid.
`confirmation_required`	No	True when the user must approve before the action runs.
`queued_conversation_ids`	No	Conversation UUIDs queued for the action.
`skipped_conversation_ids`	No	Conversation UUIDs that were skipped.
`unresolved_conversation_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / conversation_ids / description

Added value: +"Conversation UUIDs to reopen, from 1 to 100."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "affected_count": {
+      "description": "Number of records the action will change.",
+      "type": "integer"
+    },
+    "confirmation_required": {
+      "description": "True when the user must approve before the action runs.",
+      "type": "boolean"
+    },
+    "confirmation_token": {
+      "description": "Pass back as confirmation_token after the user approves.",
+      "type": "string"
+    },
+    "expires_in_seconds": {
+      "description": "How long the confirmation token stays valid.",
+      "type": "integer"
+    },
+    "message": {
+      "description": "Message describing the action or its result.",
+      "type": "string"
+    },
+    "queued": {
+      "description": "True when several conversations were queued as background jobs.",
+      "type": "boolean"
+    },
+    "queued_conversation_ids": {
+      "description": "Conversation UUIDs queued for the action.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "skipped_conversation_ids": {
+      "description": "Conversation UUIDs that were skipped.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "unresolved_conversation_ids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only but non-destructive mutation. The description adds genuinely new behavioral context: the confirmation challenge must be satisfied before the status change takes effect, and the batching expectation for multiple targets. It does not cover failure or partial-success behavior, keeping it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action and scope, followed by operational constraints and the inverse tool. Every sentence carries information; no filler.

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 values need no explanation, and annotations cover the safety profile. The description covers batching, the confirmation prerequisite, and the sibling relationship, leaving only edge-case behavior (partial failures, invalid IDs) unaddressed.

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 coverage is 100% and both parameters are already documented, including the confirmation_token challenge flow. The description only reinforces the batching semantics ('send all target conversation UUIDs in one call') rather than adding syntax or format detail, so baseline 3 is correct.

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 (reopen) and resource (resolved Chatway conversations), including multi-item scope. It explicitly names the inverse sibling resolve-conversation, so an agent can separate the two without opening either schema.

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 a clear condition and alternative: batch all UUIDs in one call, obtain user confirmation first, and use resolve-conversation to close again. It lacks an explicit 'when not to use' case, but the routing guidance is unambiguous.

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?