RunWhen Platform MCP

Get Run Status

get_run_status

Poll the status of a script run after run_script to check if execution completed, is still running, or failed.

Instructions

Check the status of a script run.

Poll this after run_script to check if execution has completed. Status values: RUNNING, SUCCEEDED, FAILED.

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>",
      "workspace_name": "<workspace_name>"
    },
    "name": "get_run_status"
  }
}

Input Schema

Name	Required	Description	Default
`run_id`	Yes	The run ID returned by run_script.
`workspace_name`	Yes	The workspace the run belongs to (e.g. 't-oncall').

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It usefully reveals the polling pattern and the terminal status values (RUNNING, SUCCEEDED, FAILED), but omits permission requirements, error behavior for an invalid run_id, and rate limits, leaving notable behavioral gaps.

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 short, front-loaded sentences with zero filler; the core purpose leads and the polling guidance and status values follow logically. Every sentence earns its place.

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?

An output schema exists, so return values need no explanation, and the description supplies the polling workflow and status vocabulary an agent needs. It is nearly complete for a simple status-check tool, with only minor gaps around error handling and auth.

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 100%, so both run_id and workspace_name are already documented in the schema. The description adds no additional parameter meaning beyond what the schema provides, which is the baseline expectation when the schema already does the heavy lifting.

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 states a specific verb and resource ('Check the status of a script run'), making the tool's function immediately clear. It references the related run_script tool as a precondition but does not explicitly distinguish itself from adjacent siblings like get_run_output or run_script_and_wait, so it falls just short of a 5.

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?

It gives clear contextual guidance: 'Poll this after run_script to check if execution has completed,' establishing when the tool fits in the workflow. However, it does not name alternatives such as run_script_and_wait (which suggests waiting outright) or state when-not to poll, so it lacks explicit exclusion guidance.

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

Deploy Server