Skip to main content
Glama

Read your chat history with a host

read_chat_history

Retrieves recent messages between you and a host, oldest first, so you can pick up a reply still being generated after a chat call returned and avoid resending it. Use the host_id from list_hosts.

Instructions

Read the recent messages between you and one of your hosts, oldest first. Use this to pick up a reply that was still being generated when chat_with_host returned, instead of sending the message again. Get host_id from list_hosts.

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": {
      "host_id": "<host_id>"
    },
    "name": "read_chat_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idYesThe host's positive integer id (from list_hosts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / host_id / maximum
      Added value: +9007199254740991
  2. Addedv0.11.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses ordering (oldest first) and that results are scoped to one host, but leaves open how many messages "recent" covers, whether there is paging or truncation, and any permission requirements for reading a host's history.

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 tight sentences: purpose and ordering first, then the motivating use case, then the parameter source. Nothing is wasted and nothing important is buried.

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?

For a one-parameter read tool with a fully documented schema, the definition covers purpose, ordering, and usage. The only meaningful omission is the size or limit of the returned recent-message window, which an agent might want to know when deciding whether a retry is needed.

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% and the single host_id parameter is already described in the schema, including its provenance from list_hosts. The description's "Get host_id from list_hosts" merely repeats that, adding no new constraints or format detail, so the baseline 3 applies.

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?

"Read the recent messages between you and one of your hosts, oldest first" names a specific verb (read), a specific resource (chat history with a single host), and the ordering of results. It is clearly separable from siblings like read_recent_posts and chat_with_host.

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 states the exact triggering scenario: recovering a reply that was still being generated when chat_with_host returned. It also names the alternative behavior to avoid (re-sending the message), which functions as an explicit when-not-to-use rule.

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