Skip to main content
Glama

run_status

Read-onlyIdempotent

Report a detached run's progress with state, completed and expected result counts, and execution errors so you can poll launches and track completion.

Instructions

Report one arm's progress: state (pending, running, completed or interrupted), completed and expected result counts, and execution errors. Use it to poll a detached run_launch; use run_results for the task rows. Read-only. Returns {run_id, version, split, state, completed, expected, errors}.

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

Input Schema

NameRequiredDescriptionDefault
configYesPath of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path.
run_idYesRun id, as returned by run_launch or named in run_interleaved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.9
    • addedInput schema / properties / config / description
      Added value: +"Path of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path."
    • addedInput schema / properties / run_id / description
      Added value: +"Run id, as returned by run_launch or named in run_interleaved."
  2. First observedv0.1.7

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint, so 'Read-only' is redundant, but the description goes further by disclosing the state enumeration, the polling use case, and the exact returned field set. It stops short of describing error semantics or how an 'interrupted' state should be handled, leaving a small gap.

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?

Three tight sentences: what it reports first, then the routing rule, then the return shape. Nothing is padded and the most decision-relevant content is front-loaded.

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

Completeness4/5

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

With no output schema, the description compensates by listing the returned keys, and the two required params are fully documented in the schema. The only omission is behavior around error/partial states, which matters modestly for a status-polling tool.

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 100% with rich per-parameter text for config and run_id, so the schema carries the semantic load. The description adds context ('one arm', 'as returned by run_launch') but no parameter-specific detail beyond that, so baseline 3 applies.

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?

'Report one arm's progress' gives a specific verb and resource, then enumerates exactly what is reported (state, completed/expected counts, execution errors) including the full state vocabulary. It is clearly distinguishable from run_results, which is named as the task-row counterpart.

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

Usage Guidelines5/5

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

'Use it to poll a detached run_launch' states the triggering condition, and 'use run_results for the task rows' names the alternative plus the criterion that selects it. An agent knows both when to call this and when to switch siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.