Skip to main content
Glama

get_run

Read-onlyIdempotent

Get the status and result of a playbook run. Use after run_playbook, or when the user asks whether an automation finished and what it produced.

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

Input Schema

NameRequiredDescriptionDefault
idYesRun ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds lifecycle context (it is the follow-up to run_playbook) but says nothing about whether runs are eventually consistent, whether polling is expected, or whether status values are terminal — all relevant 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.

Conciseness5/5

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

Two sentences, front-loaded with the core action, followed by the usage condition. Nothing is redundant or padded.

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?

For a simple one-parameter read tool with no output schema, the description covers the essentials. However, 'result' is left entirely undefined — an agent cannot tell whether the run output, a summary, or an error payload is returned, which matters for a tool whose whole purpose is retrieving a result.

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?

There is a single required parameter with 100% schema description coverage, so the schema fully documents 'id' as the Run ID. The description adds no further meaning about the identifier's format or where an agent obtains it beyond the implied link to run_playbook's output.

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 gives a specific verb and resource: 'Get the status and result of a playbook run.' This is meaningfully distinct from get_run_steps (which would presumably return step-level detail), though that sibling is never named, so differentiation is left implicit rather than stated.

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 provides explicit triggering conditions: call it after run_playbook, or when the user asks whether an automation finished and what it produced. That is concrete context for invocation, but there is no exclusion guidance (e.g., when to prefer get_run_steps over this tool).

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