Skip to main content
Glama

read_response

Read-onlyIdempotent

Stream a chunk of a pending ask() job's output.

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": {
      "job_id": "<job_id>"
    },
    "name": "read_response"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id returned by a prior ask() call.
offsetNoByte offset to start reading from. 0 for the beginning.
publisher_idNoPublisher the research is bound to. Only the dedicated research credential may send it; other callers are refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / publisher_id
      Added value: +{
      +  "description": "Publisher the research is bound to. Only the dedicated research credential may send it; other callers are refused.",
      +  "type": "number"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/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 meaningful chunked/streaming behavior, but omits how an agent knows the stream is complete, what happens if the job is still running or has expired, and whether chunks are ordered or repeatable.

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?

A single, front-loaded sentence with no filler; the verb and the object arrive immediately. Nothing is wasted.

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 streaming reader with no output schema, the description leaves the critical operational facts unstated: what a chunk contains, how termination is signalled, and how offset interacts with successive reads. The safety metadata is present, but the streaming contract an agent needs to call this correctly in a loop is missing.

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 job_id, offset and publisher_id are already fully documented; baseline 3 applies. The description adds only the linkage that the job_id comes from ask() and that output is read in chunks, which the schema's offset text already conveys.

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 ("Stream") plus the resource ("a chunk of a pending ask() job's output") and ties itself to the producing tool ask(), which helps place it relative to siblings. It stops short of explicitly contrasting with request_status, so an agent must infer which one reports job state versus which one yields payload.

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 is only implied: "pending ask() job's output" suggests calling it after ask() returns a job_id. There is no statement of when to prefer request_status, no guidance on looping/re-reading as the job progresses, and no exclusion of cases (finished jobs, failed jobs).

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