Chatway Live Chat

Check Chatway Connection

check-connection

Read-onlyIdempotent

Check whether the current MCP session has an active Chatway connection. Use this when Chatway inbox tools are unavailable or authentication may have expired.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`status`	No
`message`	No
`connected`	No
`connection_id`	No	Chatway connection UUID.
`connection_name`	No
`disconnected_at`	No	ISO 8601 timestamp.
`assistant_guidance`	No	What the assistant should do next.
`reconnect_required`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "assistant_guidance": {
+      "description": "What the assistant should do next.",
+      "type": "string"
+    },
+    "connected": {
+      "type": "boolean"
+    },
+    "connection_id": {
+      "description": "Chatway connection UUID.",
+      "type": "string"
+    },
+    "connection_name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "disconnected_at": {
+      "description": "ISO 8601 timestamp.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "reconnect_required": {
+      "type": "boolean"
+    },
+    "status": {
+      "enum": [
+        "connected",
+        "unauthenticated",
+        "disconnected",
+        "not_authorized"
+      ],
+      "type": "string"
+    }
+  },
+  "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 readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the useful scoping detail that the check is about the current MCP session and is a diagnostic fallback, which is context beyond 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?

Two short sentences, purpose first and trigger second, with no filler.

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 with no parameters and full annotation coverage the description supplies everything an agent needs to decide to call it.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: checks whether the current MCP session has an active Chatway connection. This clearly separates it from the inbox-action siblings, though it doesn't explicitly name them as alternatives.

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 concrete trigger: use when Chatway inbox tools are unavailable or auth may have expired. That is clear context, but it stops short of explicit exclusions (e.g. don't poll it routinely).

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?