Chatway Live Chat

Search Conversations

search-conversations

Read-only

Search accessible Chatway conversations by email subject, origin URL, or contact name/email. This does not search message bodies; use returned conversation IDs to retrieve messages. Use list-conversations to browse recent conversations or filter them by status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum results to return, from 1 to 50.
`query`	Yes	Search term for conversation subject, URL, or contact.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`conversations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum results to return."New value: +"Maximum results to return, from 1 to 50."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "conversations": {
+      "items": {
+        "properties": {
+          "contact": {
+            "properties": {
+              "email": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "id": {
+                "description": "Visitor/contact UUID.",
+                "type": "string"
+              },
+              "name": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "email_subject": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "is_resolved": {
+            "type": "boolean"
+          },
+          "origin": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "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 cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuinely useful negative capability disclosure — the search index covers subject/URL/contact only, not message bodies. It does not mention result limits or ordering, but the schema documents the limit parameter.

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 sentences, each earning its place: capability and search scope first, the body-search limitation second, the routing alternative third. No filler and no 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?

With an output schema present, return values need not be explained, and the description covers scope, exclusion, and sibling routing. Nothing needed to invoke it correctly is missing.

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% (both query and limit are documented), so the schema carries parameter semantics. The description restates the searchable fields, which only marginally extends the schema's own wording about subject/URL/contact.

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 (search) and resource (conversations) plus the exact searchable fields (email subject, origin URL, contact name/email), and explicitly contrasts with list-conversations and message retrieval, so the agent can distinguish it from siblings without opening any 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?

Explicitly states when NOT to use it ('does not search message bodies; use returned conversation IDs to retrieve messages') and names the alternative for browsing/filtering ('use list-conversations'). Both the exclusion and the alternative are named with the condition that selects them.

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?