Chatway Live Chat

Search Contacts

search-contacts

Read-only

Search accessible Chatway contacts by name, email address, or phone number. Returns matching contact records but does not search conversation messages. Use get-visitor instead when you already have the contact's UUID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum results to return, from 1 to 50.
`query`	Yes	Search term for contact name, email, or phone.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`contacts`	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": {
+    "contacts": {
+      "items": {
+        "properties": {
+          "email": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "phone": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "widget_id": {
+            "type": [
+              "integer",
+              "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, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful scope context ('accessible' contacts implying permission-filtered results and what is returned), though it says nothing about limit/pagination behavior beyond the schema.

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 compact sentences with zero filler; the resource and match scope are front-loaded before the exclusions and alternative.

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 full annotation coverage, a 100%-covered two-parameter schema, and an output schema present, the description supplies everything an agent needs to select and invoke this tool correctly.

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%, so both parameters are already documented in the schema. The description mirrors the match fields for `query` but adds no syntax or format detail beyond it, making the baseline 3 appropriate.

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 ('Search accessible Chatway contacts') and narrows the match fields to name, email, or phone. It explicitly distinguishes itself from search-conversations ('does not search conversation messages') and get-visitor, so an agent can select it without opening schemas.

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?

Names the when-not condition and the alternative directly: 'Use `get-visitor` instead when you already have the contact's UUID.' It also rules out the neighboring search domain (conversation messages), leaving nothing to inference.

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?