Skip to main content
Glama

read_thread

Read the private ordered message, offer and sale history, plus current allowed actions. Acknowledges only the visible returned events across website and MCP. Reading is free and never approves an offer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
lot_idNo
saleIdNo
max_feeNo
conversation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / $defs / 0
      Added value: +{
      +  "maxLength": 256,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / lot_id
      Added value: +{
      +  "$ref": "#/$defs/0"
      +}
    • addedInput schema / properties / saleId / $ref
      Added value: +"#/$defs/0"
    • removedInput schema / properties / saleId / maxLength
      Removed value: -256
    • removedInput schema / properties / saleId / minLength
      Removed value: -1
    • removedInput schema / properties / saleId / type
      Removed value: -"string"
  2. Added

TDQS

B3.1/5.0
Behavior4/5

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

With readOnlyHint=false supplied, the description usefully explains why: the call 'acknowledges' visible events, which is a side effect, and it explicitly states reading is free and 'never approves an offer.' It also scopes the result to events visible across website and MCP. It does not cover whether acknowledgment is reversible or whether the free-read claim holds under limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core content front-loaded and no filler. The second sentence's phrasing ('Acknowledges only the visible returned events across website and MCP') is compact but ambiguous enough to cost a point.

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

Completeness2/5

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

For a six-parameter, zero-required tool with no output schema and no parameter documentation, the description does far too little: it never clarifies how the id parameters interact, what 'allowed actions' means structurally, or how pagination behaves.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

None of the six parameters (after, limit, lot_id, saleId, max_fee, conversation_id) is explained, and schema description coverage is 0%. The mention of 'offer and sale history' only faintly hints at saleId/lot_id, leaving pagination (after/limit) and max_fee entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Read') and enumerates the resources returned: message, offer and sale history, and current allowed actions. It is distinguishable from siblings like manage_thread or list_inbox, though the phrase 'private ordered message' is awkward and slightly obscures what is actually read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to call this versus manage_thread, list_inbox, or respond; the closest hint is that it surfaces 'current allowed actions,' implying it precedes acting. No prerequisites or exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources