Skip to main content
Glama
DOC Model Safety Gate

DOC Model Safety Gate

by laceykes

getNodeRuns

Retrieve node-level results for a specific workflow run to inspect each node's outcome and status.

Instructions

Get node-level run results for 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": "getNodeRuns"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.1/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. The verb 'Get' implies a read, but nothing is said about whether results are truncated or paginated, whether node outputs can be large, whether failed or skipped nodes are included, or what a caller gets back for an in-progress run. For a read tool with zero annotation coverage and no output schema, this leaves the agent guessing at the response shape.

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?

A single tight sentence with the resource and scope front-loaded and no filler. It is efficient, though the brevity is partly under-specification rather than pure economy.

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 place a caller could learn what the results look like or how to handle partial/failed runs, and it provides none of that. It is adequate to identify the tool's intent but insufficient to predict or interpret its output.

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 baseline is 3. The description adds only that runId scopes to a workflow run, which the schema field name already conveys; no format, source, or lookup guidance is added.

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: 'Get node-level run results for a workflow run'. 'Node-level' meaningfully separates it from the sibling getRunStatus, which presumably reports overall run state rather than per-node output. It stops short of naming that sibling, so the differentiation is inferable rather than explicit.

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

Usage Guidelines3/5

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

Usage is implied: call this when you need per-node output for a specific workflow run. There is no statement of when not to use it, no mention of getRunStatus as the lighter alternative, and no prerequisites such as run state (e.g. only after the run completes).

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