Skip to main content
Glama

Get workflow run

get_run
Read-only

A workflow run: status (queued, running, completed, failed, canceled), each step's status, generation request and outputs, the run's named outputs, and credits. wait=true polls up to timeout_s (max 600).

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

Input Schema

NameRequiredDescriptionDefault
waitNo
run_idYes
timeout_sNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's real contribution is the blocking behavior: wait=true polls up to timeout_s with a hard cap of 600 seconds. That is meaningful context an agent needs before issuing a call that may block, though it omits whether polling returns early on terminal status or what happens if the run is never found.

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?

Two tight sentences, no filler; the terminal-status enum is inlined compactly and the polling constraint is stated once. It is appropriately short for a single-resource fetch.

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, so the heavy field enumeration in the description is partly redundant, while genuinely needed details (run_id semantics, polling return conditions) are absent. Adequate for a simple three-parameter read, but not complete.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it does explain wait and the timeout_s cap of 600. However it never describes run_id (the sole required parameter), its format, or the default timeout of 300, leaving the most important input 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 names the resource (a workflow run) and enumerates exactly what a caller retrieves: status, per-step status, generation request/outputs, named outputs, and credits. The retrieval verb is only implied by the name and title rather than stated, and no sibling (list_runs, get_job, wait_for_job) is contrasted, so it stops 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 Guidelines2/5

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

There is no guidance on when to call this versus list_runs or wait_for_job; the only usage-like statement is the wait=true polling behavior, which is parameter semantics rather than tool selection guidance. An agent must infer the use case from the field list.

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