Chatway Live Chat

Search Conversations

search-conversations

Read-onlyIdempotent

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

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

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 declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it searches only accessible conversations and does not search message bodies, directing the agent to use returned IDs for message retrieval. It does not add auth/rate-limit details, but those are less critical here.

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, front-loaded with the core search behavior, followed by the key limitation and the relevant alternative. Every sentence adds information an agent needs, with no redundant restatement of the tool name.

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?

The tool is a straightforward search endpoint with an output schema, full input schema coverage, and annotations covering safety. The description supplies the important missing behavioral nuance: it does not search message bodies, and `list-conversations` is the browsing alternative. Nothing material is absent.

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 in the input schema. The description adds minor precision by naming the searchable fields as email subject, origin URL, and contact name/email, but it does not explain `limit` beyond what the schema already provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb and resource: search accessible Chatway conversations. It then lists searchable fields (email subject, origin URL, contact name/email) and explicitly distinguishes the scope from message-body search, so an agent can identify what this tool does without opening the 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?

It gives clear usage guidance: search conversations by subject/URL/contact, do not use it for message bodies, use returned conversation IDs to retrieve messages, and use `list-conversations` for browsing or status filtering. These are explicit alternatives and exclusions.

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?