Skip to main content
Glama

read_step_output

Retrieve truncated step output or input by specifying step ID, offset, and character limit to get full context from a campaign DAG.

Instructions

Read a range from a step's output (or input) field.

Counterpart to the preview-plus-seek contract in get_my_context: when an upstream preview is truncated, call this with the step_id from the preview to pull the full (or a slice of) text.

Args: step_id: The step whose output you want to read. Does not have to be your own step — any step in the same campaign's DAG is readable. offset: 0-indexed character offset to start from. limit: Max characters to return (default 8000, capped at 32000 to avoid blowing the agent's context). field: "output" (default) or "input".

Returns::

{
    "step_id": N,
    "field": "output",
    "content": "...",
    "offset": 0,
    "limit": 8000,
    "total_chars": N,
    "has_more": bool,  # True if offset+limit < total_chars
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
step_idYes
offsetNo
limitNo
fieldNooutput

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that any step in the campaign DAG is readable, explains the `limit` cap (32000), and describes the return format with `has_more`. However, it doesn't mention authentication or rate limits, which are implied but not stated.

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?

The description is well-structured with a one-line purpose, a usage paragraph, concise bulleted Args, and a Returns block. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters, no nested objects, and a provided output schema (described in text), the description covers purpose, usage, parameters, and return format. It ties into the sibling tool's contract, leaving no critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description fully explains each parameter: `step_id` (any campaign step), `offset` (0-indexed), `limit` (default and cap), `field` (default 'output' or 'input'). This adds essential meaning beyond the schema.

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?

The description clearly states 'Read a range from a step's ``output`` (or ``input``) field', specifying a verb, resource, and distinguishing from the sibling `get_my_context` by referencing the preview-seek contract.

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?

Provides explicit usage context: 'when an upstream preview is truncated, call this with the ``step_id`` from the preview to pull the full text'. It references the sibling tool as the counterpart, but doesn't exhaustively list all when-not situations.

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/retospect/sortie-mcp'

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