Skip to main content
Glama
Sign In

Chatway Live Chat

by app.chatway.mcp
OverviewDiscussionsAdmin

Unresolve Conversation

unresolve-conversation
Destructive

Reopen one or more resolved Chatway conversations. Send all target conversation UUIDs in one call. Calls with more than one conversation require user confirmation; a single conversation is reopened immediately. Use resolve-conversation to close them again.

Input Schema

NameRequiredDescriptionDefault
conversation_idsYesConversation UUIDs to reopen, from 1 to 30.
confirmation_tokenNoOnly for calls with more than one conversation: required after the confirmation challenge. Ask the user to approve before calling again with this token.

Output Schema

NameRequiredDescriptionDefault
queuedNoTrue when several conversations were queued as background jobs.
messageNoMessage describing the action or its result.
affected_countNoNumber of records the action will change.
confirmation_tokenNoPass back as confirmation_token after the user approves.
expires_in_secondsNoHow long the confirmation token stays valid.
confirmation_requiredNoTrue when the user must approve before the action runs.
queued_conversation_idsNoConversation UUIDs queued for the action.
skipped_conversation_idsNoConversation UUIDs that were skipped.
unresolved_conversation_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirmation_token / description
      Previous value: -"Required after the confirmation challenge. Ask the user to approve before calling again with this token."New value: +"Only for calls with more than one conversation: required after the confirmation challenge. Ask the user to approve before calling again with this token."
  2. Changed1 schema field changed
    • changedInput schema / properties / conversation_ids / description
      Previous value: -"Conversation UUIDs to reopen, from 1 to 100."New value: +"Conversation UUIDs to reopen, from 1 to 30."
  3. Changed2 schema fields changed
    • 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"
+}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructive=true and non-idempotent, but the description adds the non-obvious confirmation gate: multi-conversation calls require user approval while a single conversation 'is reopened immediately'. That asymmetry is real behavioral context an agent cannot infer from the schema alone. It does not describe what state the conversation returns to, a minor gap given the destructive hint.

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?

Four short sentences, front-loaded with the action, then the batching rule, then the confirmation caveat, then the inverse tool. No filler or redundancy.

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?

With an output schema present, return values need no explanation, and the description covers action, batching, confirmation workflow, and the inverse tool. Only the post-reopen conversation state is left implicit.

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%, including the 1-to-30 range and the confirmation_token challenge flow, so the schema does the heavy lifting. The description only reinforces that IDs should be batched into one call rather than adding syntax or format detail.

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?

Specific verb and resource: 'Reopen one or more resolved Chatway conversations.' It names the exact target state (resolved) and the exact action (reopen), making it immediately distinguishable from resolve-conversation among 20+ 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?

Explicitly routes the agent to the inverse tool ('Use resolve-conversation to close them again') and gives a batching rule ('Send all target conversation UUIDs in one call'), so the agent knows both the alternative and the preferred calling pattern.

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 toolsInspect
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