Skip to main content
Glama

Get a StewAI Run Step Chunk

get_run_step_chunk
Read-onlyIdempotent

Read one signed continuation chunk for an oversized run step result.

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>",
      "chunk_ref": "<chunk_ref>"
    },
    "name": "get_run_step_chunk"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
chunk_refYes

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 read-only, idempotent, non-destructive, and closed-world behavior. The description adds that chunks are 'signed' and are continuations of oversized results, but it does not disclose ordering, expiry, pagination, or how many chunks may exist.

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 definition is a single front-loaded sentence with no wasted words. It is efficiently structured, though its terseness contributes to gaps elsewhere.

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 and annotations cover the safety profile, so return values and mutation risk need not be explained. However, for a two-parameter continuation tool with zero schema descriptions, the definition should say more about chunk sequencing and how chunk_ref is obtained.

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

Parameters2/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. It hints that chunk_ref identifies a signed continuation chunk and run_id relates to the run, but it does not explain the run_id format or how chunk_ref is produced, leaving both parameters substantially undocumented.

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 uses a specific verb and resource: 'Read one signed continuation chunk for an oversized run step result.' This distinguishes it from get_run_step by scoping it to continuation chunks of oversized results, though it does not explicitly name the sibling or contrast behavior.

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?

The phrase 'for an oversized run step result' implies when the tool applies, but it does not explain how to obtain a chunk_ref, whether get_run_step must be called first, or how continuation chunks are sequenced. Usage is implied 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