Skip to main content
Glama

Get a StewAI Run Step

get_run_step
Read-onlyIdempotent

Read one sanitized full step result from an owned run by exact step identifier.

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>",
      "step_id": "<step_id>"
    },
    "name": "get_run_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
step_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds two useful traits beyond that: results are 'sanitized' (i.e., redacted) and access is restricted to 'owned' runs. It stops short of noting size limits or what a sanitized payload omits.

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; every qualifier ('sanitized', 'full', 'owned', 'exact') carries meaning.

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?

With an output schema present, return values need no explanation and the tool itself is simple (two required strings). However, the description omits how to obtain a step_id and gives no routing signal versus get_run_step_chunk, leaving an agent to infer sibling choice.

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 description coverage is 0%, so the description must compensate for two undocumented parameters. It does partially: 'owned run' clarifies that run_id must reference the caller's own run, and 'exact step identifier' signals exact-match semantics rather than a name or index lookup. It still doesn't explain the 26-character identifier format or how step ids are obtained.

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?

States a specific verb and resource ('Read one ... step result') with scope qualifiers ('sanitized full step result', 'owned run', 'exact step identifier'). The word 'full' implicitly contrasts with the chunked sibling get_run_step_chunk, though no sibling is named outright.

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

Usage Guidelines2/5

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

The description explains what the tool does but gives no when-to-use guidance: it never says to prefer this over get_run_step_chunk or how to discover step ids (e.g., via list_run_steps). The only usage hint is that an exact identifier is required, which is inferred rather than stated.

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