Retrieve terminal scrollback content from a specified Wave block to review command history or output. Optionally return only the last command's output.
Get terminal scrollback content from a Wave block. Requires the Seashell Helper block.
| Name | Required | Description | Default |
|---|---|---|---|
| block_id | Yes | Block ID to get scrollback from | |
| last_command_only | No | Return only the output of the last command (default: false) |
Changes observed during successful MCP inspections.
v2.2.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It implies a read-only operation via 'Get' and discloses an important dependency (Seashell Helper), but it does not describe return format, scrollback limits, or error behavior.
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?
Two short sentences with zero waste, and the primary purpose is front-loaded before the dependency requirement.
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?
For a simple two-parameter read tool, the description covers purpose and a key prerequisite. Without an output schema, though, it should say more about what scrollback content is returned or any limits, leaving a noticeable gap.
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 coverage is 100%, so both parameters are already documented in the input schema. The description adds no additional meaning about block_id or last_command_only beyond what the schema provides, making baseline 3 appropriate.
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 states a clear verb ('Get') and resource ('terminal scrollback content') scoped to a Wave block. It distinguishes from generic command execution tools by naming scrollback specifically, though it does not explicitly contrast with siblings like get_command_output.
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?
It gives the prerequisite ('Requires the Seashell Helper block'), which is useful context for when the tool is usable. However, it does not say when to choose this over alternatives such as get_command_output or wave_run_in_block, leaving selection to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.