Skip to main content
Glama

read_output

Read new output from a running command without sending input. Use it to poll long-running processes after the initial execution returns a partial status.

Instructions

Read new output from a running command without sending any input.
Use this after execute returns status "partial" when the command needs no interaction
(e.g. long-running build, training loop, find).

Returns the same format as execute/respond.

Args:
- pause_timeout: seconds of OUTPUT SILENCE before returning (default 9.0).
  This is the dial that controls how long a silent-poll call waits.
  Raise it (e.g. 30, 60) when polling a very quiet job; raising
  total_timeout instead does nothing while the process stays silent.
- total_timeout: hard cap on call duration (default 20.0). Only binds
  while output is actively streaming.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
command_idYesThe active command_id returned in a partial status response
pause_timeoutNoSeconds of output silence to wait before returning (default is 9.0)
total_timeoutNoHard cap in seconds on the maximum duration of this call (default is 20.0)
Behavior4/5

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

No annotations provided, so description carries the burden. Clearly explains return format matches execute/respond, and details behavior of pause_timeout vs total_timeout. No contradictions.

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?

Six sentences, no fluff. Front-loaded with purpose and usage, then parameter details. Every sentence adds value.

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, but description mentions return format. Covers all parameters. Could mention error conditions, but given low complexity, it's adequate.

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?

Schema coverage is 100%, baseline 3. Description adds extra semantics: explains pause_timeout as 'OUTPUT SILENCE' and clarifies that raising total_timeout does nothing while process is silent.

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?

Clearly states 'Read new output from a running command without sending any input.' Distinguishes from sibling tools like execute and respond by the 'without sending any input' qualifier.

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

Usage Guidelines4/5

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

Explicitly says 'Use this after execute returns status partial' and gives examples (long-running builds). Does not explicitly state when not to use, but context makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/QiuwenZheng/interminal'

If you have feedback or need assistance with the MCP directory API, please join our Discord server