Chatway Live Chat

Get Contact Details

get-visitor

Read-only

Retrieve one Chatway visitor/contact profile by visitor UUID, including the profile data available to the authenticated connection. Use this when you already have the visitor UUID (for example contact.id from get-conversation); otherwise find the contact with search-contacts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`visitor_id`	Yes	UUID of the visitor/contact, for example `contact.id` from `get-conversation` or `id` from `search-contacts`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`visitor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

changedInput schema / properties / visitor_id / description

Previous value: -"The UUID of the visitor/contact."New value: +"UUID of the visitor/contact, for example `contact.id` from `get-conversation` or `id` from `search-contacts`."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "visitor": {
+      "properties": {
+        "country": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "created_at": {
+          "description": "ISO 8601 timestamp.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "email": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "type": "string"
+        },
+        "language": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "phone": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "timezone": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "widget_id": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "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=true and destructiveHint=false, so the safety profile is covered; the description adds that returned fields are scoped to 'the profile data available to the authenticated connection,' which signals permission-dependent output that annotations do not convey. It stops short of describing not-found behavior or error modes, but with annotations and an output schema present the bar is lower.

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 sentences, zero filler, and the primary action and its input requirement are front-loaded before the alternative is introduced. Every clause earns its place by either defining scope or routing to a sibling.

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 no explanation; annotations cover the safety profile; the single parameter is fully documented; and the sibling routing is explicit. Nothing an agent needs in order to select and invoke this tool 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 description coverage is 100%, and the schema itself already documents visitor_id as the visitor/contact UUID with the same sourcing examples, so the description adds no new parameter detail. Baseline 3 is appropriate when the schema carries the semantics.

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 (Retrieve) and resource (one Chatway visitor/contact profile) with singular scope, and implicitly distinguishes itself from the plural lookup sibling search-contacts. An agent can tell from the description alone that this is a single-record fetch keyed by UUID.

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 to use it ('when you already have the visitor UUID') and where that UUID comes from ('contact.id from get-conversation'), then names the alternative ('otherwise find the contact with search-contacts'). This is a full when/when-not/alternative routing statement.

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?