Skip to main content
Glama
DOC Model Safety Gate

DOC Model Safety Gate

by laceykes

getRunStatus

Retrieves the status and details of a workflow run using its run ID, helping you monitor staged content changes awaiting human review or approval.

Instructions

Get the status and details of a workflow 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": {
      "runId": "<runId>"
    },
    "name": "getRunStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses very little. 'Get' implies a read, but the description never says what status values exist, whether 'details' includes node-level output, or whether the call is cheap enough to poll — all of which matter for a run-status tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the resource front-loaded and no filler. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only source of information about return shape, and 'status and details' is too vague to tell an agent what it will receive. For a run-inspection tool surrounded by run/node siblings, more precision about the returned fields was needed.

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% with a single required runId, so the schema already does the parameter work. The description adds no meaning about runId format or scope (e.g. whether it accepts a run name or composite id), which is the baseline 3 case.

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 ('Get') and resource ('status and details of a workflow run'), so an agent knows this retrieves run-level state. It does not distinguish itself from near neighbors like getNodeRuns or getWorkflow, so sibling differentiation is left to the name alone.

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?

There is no when-to-use guidance at all: nothing says whether this is for polling a run in progress, checking a completed run's outcome, or when to prefer getNodeRuns for step-level detail. The agent must infer the choice from names.

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