Skip to main content
Glama
Sign In

Chatway Live Chat

by app.chatway.mcp
OverviewDiscussionsAdmin

Resolve Conversation

resolve-conversation
Destructive

Mark one or more Chatway conversations as resolved. Send all target conversation UUIDs in one call. Calls with more than one conversation require user confirmation; a single conversation is resolved immediately. Use unresolve-conversation to reopen conversations.

Input Schema

NameRequiredDescriptionDefault
conversation_idsYesConversation UUIDs to resolve, 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.
resolved_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 resolve, from 1 to 100."New value: +"Conversation UUIDs to resolve, from 1 to 30."
  3. Changed2 schema fields changed
    • 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"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, but the description adds genuinely new behavior beyond them: the two-tier confirmation model (multi-conversation calls require user confirmation, single calls do not) and the batching expectation. It stops short of describing side effects such as whether resolution notifies participants or closes the thread, which would be the remaining useful detail.

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?

Four short sentences, front-loaded with the action and followed by the batching and confirmation rules, with no filler. Slightly dense in the middle sentence where the confirmation rule and immediacy rule are compressed together.

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 and the schema fully documents both parameters, so the description's job is mainly the confirmation workflow and it covers that well. It does not say what happens when a confirmation_token is missing, expired or invalid, leaving the failure path unaddressed for a destructive operation.

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% and the schema already documents both the 1-30 UUID range and the purpose of confirmation_token. The description reinforces the batching intent for conversation_ids but adds no syntax or format detail beyond what the schema states, so it sits at the baseline.

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 ... conversations as resolved") and names the sibling that does the opposite ("Use `unresolve-conversation` to reopen conversations"), so an agent can distinguish the pair 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 operational guidance: batch all target UUIDs into one call, expect a confirmation challenge when resolving more than one conversation, and single conversations resolve immediately. It also names the alternative tool for the inverse operation, covering both when-to-use and when-to-use-something-else.

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