Conciergr

Read a chat

read_chat

Read-only

One chat's messages (the customer's, the assistant's and the team's), its open request if any, and whether the family has signed up. Up to 300 messages at a time (max 1,000); pass the oldest message id as before for earlier ones. Photos, voice notes and files can be fetched with get_chat_file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contact": "<contact>"
    },
    "name": "read_chat"
  }
}

Input Schema

Name	Required	Description
`brand`	No	Which assistant (its slug from get_overview `brands[].slug`). Leave out when the business has one.
`limit`	No
`before`	No
`contact`	Yes	The chat's contact key, from list_chats, list_needs_you or search_chats (`contact`).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, non-destructive, closed-world), and the description adds the real behavioral detail an agent needs: a default page of up to 300 messages, a hard cap of 1,000, and the cursor semantics for paging backwards. Still silent on error behavior when the contact key is unknown or the chat is empty.

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 compact sentences, front-loaded with the payload contents, then pagination, then the sibling escape hatch for files. No filler and nothing repeated from annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description correctly spends its words describing the returned shape (messages, open request, signup flag). Combined with pagination and the file-fetch pointer, this is nearly complete; only edge-case behavior is unaddressed.

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?

Schema coverage is 50% (brand and contact documented, limit and before not). The description compensates well by explaining that 'before' takes the oldest message id and that limit governs 300-per-page up to 1,000, which is more than the bare integer schema conveys.

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 (read one chat) and enumerates exactly what comes back: messages from three participant types, the open request, and signup status. This clearly separates it from list_chats/search_chats, and it points to get_chat_file for attachments.

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 concrete pagination guidance ('pass the oldest message id as before for earlier ones') and routes attachment retrieval to get_chat_file. It does not explicitly say when to prefer search_chats/list_chats over this tool, but the read-one-chat context makes that implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Conciergr 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?