Chatway Live Chat

Resolve Conversation

resolve-conversation

Destructive

Mark one or more Chatway conversations as resolved. Send all target conversation UUIDs in one call. This is destructive and requires user confirmation. Use unresolve-conversation to reopen conversations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`conversation_ids`	Yes	Conversation UUIDs to resolve, 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.
`resolved_conversation_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

changedInput schema / properties / conversation_ids / description

Previous value: -"Conversation UUIDs to resolve."New value: +"Conversation UUIDs to resolve, 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"
+    },
+    "resolved_conversation_ids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "skipped_conversation_ids": {
+      "description": "Conversation UUIDs that were skipped.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'This is destructive' is partly redundant. However it adds genuinely new behavioral information: that user confirmation is required and that a follow-up call with a token is expected, which is not expressed anywhere in the annotations.

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, all front-loaded: action first, batch constraint second, destructive/confirmation warning third, sibling routing last. No filler or repetition.

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?

An output schema exists, so return values need no explanation, and the confirmation workflow is fully described. For a two-parameter destructive tool, everything an agent needs to call it correctly is present.

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 both parameters are already documented, including the 1-100 range and the confirmation_token flow. The description's only added meaning is that all UUIDs belong in a single batch call; beyond that it does not extend 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 resource ('Mark ... Chatway conversations as resolved') and immediately clarifies batch semantics ('one or more'). The final sentence explicitly contrasts with the sibling unresolve-conversation, so an agent can disambiguate 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 Guidelines5/5

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

Gives explicit invocation guidance ('Send all target conversation UUIDs in one call') and names the alternative tool plus the condition that selects it ('Use unresolve-conversation to reopen conversations'). When-to-use and the inverse case are both covered.

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?