Skip to main content
Glama

List StewAI Run Steps

list_run_steps
Read-onlyIdempotent

Page through sanitized step summaries or full step results from one owned run.

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": {
      "run_id": "<run_id>"
    },
    "name": "list_run_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoSteps per page for view=steps: default 10, at most 20.
cursorNo
detailNoFor view=steps: summary (default) lists each step's id, title, kind, status, timing and result type; full returns parameters, rendered input and result. view=step always returns the full step.
run_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds two pieces of context they don't: results are 'sanitized' (a redaction guarantee) and access is limited to 'one owned run' (an implicit authorization scope). It still omits cursor/pagination mechanics and any rate-limit behavior.

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 paging verb and the two output granularities lead the sentence. Nothing is redundant.

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

Completeness3/5

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

An output schema exists so return shape needn't be described, but for a four-parameter paginated list tool the definition leaves cursor semantics and the summary-vs-full tradeoff (cost, size) unexplained. Adequate to call correctly, thin for calling efficiently.

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 50% — limit and detail are documented in-schema, while cursor and run_id are not. The description's 'summaries or full step results' mirrors the detail enum but adds no syntax or format detail beyond the schema, so it neither compensates for the gap nor misleads.

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 ('Page through') and resource ('sanitized step summaries or full step results') scoped to 'one owned run', which is clearly distinguishable from a single-step fetch. It stops short of naming the single-step or diagnostics siblings it competes with, so an agent must infer the boundary.

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 implied by the words 'Page through' — use this to enumerate all steps of a run rather than retrieve one — but the definition never states when to prefer it over get_run_step or get_run_diagnostics. No exclusions, no prerequisites beyond the vague 'owned run'.

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