Retrieve paginated terminal output (stdout/stderr) for any active or recently completed process to inspect command results. Use line_offset and line_count to navigate large logs efficiently.
Read paginated stdout/stderr captured for an active or recently completed terminal session.
| Name | Required | Description | Default |
|---|---|---|---|
| line_count | No | ||
| process_id | Yes | ||
| line_offset | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, lowering the burden on the description. The description adds meaningful extras: output is paginated, captures stdout/stderr, and is available only for active or recently completed sessions, implying a session-lifetime limitation. This is useful beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no wasted words. It states the action, the data, and the temporal scope compactly while remaining readable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the core purpose and session-scope constraint, which is adequate for a simple read tool. However, it leaves important context unstated, such as how the pagination parameters map to output and how process_id relates to a shell session, and there is no output schema to fill those gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, but it only says 'paginated' and does not explain process_id, line_count, or line_offset. The parameter names and default values are somewhat self-explanatory, but the meaning of process_id as the terminal session identifier is not clarified.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Read') and names a concrete resource ('paginated stdout/stderr captured for an active or recently completed terminal session'). It clearly differentiates this from sibling tools like lb_shell_input, lb_shell_sessions, and lb_shell_kill without needing to open the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'active or recently completed terminal session' gives useful context about when the tool applies, but it does not explicitly state when to use this tool versus alternatives such as lb_shell_sessions or lb_run_shell. No exclusions or alternative-selection guidance are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.