LIVEAIHELP — Hire a Live Human Expert

Read expert messages

read_messages

Read-onlyIdempotent

Read new chat messages from the human expert. Poll this after sending a message to get the expert's reply. Returns the session status too — when status becomes ended or cancelled, stop polling and wrap up.

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": {
      "session_id": "<session_id>"
    },
    "name": "read_messages"
  }
}

Input Schema

Name	Required	Description	Default
`after`	No	ISO timestamp — only return messages after this time. Omit on first call.
`session_id`	Yes	The session_id from hire_human_expert.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the description need not restate safety. It adds valuable context by describing the polling pattern and that the call returns session status, including the terminal states that should end the interaction. It does not explain message ordering or output shape, but that is a minor gap.

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 short sentences, front-loaded with the core action, followed by usage guidance and termination conditions. Every sentence contributes useful information.

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?

No output schema exists, so the description carries some responsibility for return behavior; it does mention that session status is returned and defines terminal statuses. It could say more about message format or polling cadence, but it is sufficient to call the 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 (session_id and after) are already fully documented in the schema. The description implies incremental polling via 'new messages' but adds no format or semantic detail beyond the schema, so the baseline 3 is 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 ('Read new chat messages from the human expert') and makes the tool's role distinct from siblings like send_message and end_session. It also clarifies scope ('new messages') beyond the bare name.

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 says to poll after sending a message and gives a clear stop condition: when status becomes ended or cancelled, stop polling and wrap up. This is actionable when-to-use and when-to-stop guidance.

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

All LIVEAIHELP — Hire a Live Human Expert 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?