Skip to main content
Glama

response_read

Read-onlyIdempotent

Read a stored host response by field path with offset-based paging, then follow next_offset until more=false to collect complete results across conversations and restarts.

Instructions

Read a stored complete host response by literal field path and next_offset; available across conversations and restarts. offset is nonnegative; limit and text_limit are positive requested upper bounds. Pages use at most 50 items/4096 text characters and may be smaller to fit the host. Follow next_offset until more=false.

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": {
      "response_id": "<response_id>"
    },
    "name": "response_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
limitNo
offsetNo
text_limitNo
response_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond that: persistence across conversations and restarts, hard page ceilings of 50 items / 4096 text characters, and that pages may be smaller than requested to fit the host. The bounds on offset and the positivity constraint on limit/text_limit are stated as invariants, which is exactly the kind of detail annotations cannot express.

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?

Four sentences, front-loaded with the core action and terminating in the pagination contract, with no filler. It is densely packed into semicolon-joined clauses, which costs a little readability but wastes no words.

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 five-parameter read tool with an output schema already present, the description supplies enough: addressing model, bound semantics, and the paging loop termination condition. The only real hole is the required response_id, whose meaning and provenance an agent must guess.

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?

With 0% schema description coverage the description has to carry the parameter meaning, and it largely does: path is a literal field path, offset is nonnegative, limit and text_limit are positive requested upper bounds subject to server-side ceilings. The one required parameter, response_id, is never explained, and 'next_offset' is referenced without stating it is a returned field rather than an input.

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 gives a specific verb and resource: read a stored complete host response, addressed by literal field path and offset. That is far more concrete than the tool name alone. It stops short of naming a sibling tool (e.g. file_read) to contrast against, so the agent must infer the split itself.

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

Usage Guidelines3/5

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

Usage guidance is procedural rather than selective: 'Follow next_offset until more=false' tells the agent how to page, and 'available across conversations and restarts' hints at scope. There is no statement of when to prefer this over file_read or operation_read, nor any exclusion.

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