Skip to main content
Glama

get_run

Read-only

Retrieve a run's status and, when a test failed, identify the failing step and reason using the run id returned by run_test or run_group.

Instructions

A run's status and, when a test failed, which step and why. Pass the run id run_test or run_group returned.

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
run_idYesRun id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the burden of describing output, and it does: status always, plus the failing step and reason conditionally. That conditional return shape is the key behavioral fact for an agent deciding whether to call it. Minor gap: nothing about behavior for an unknown or still-pending run id.

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 short sentences with no filler: the first front-loads what is returned, the second tells you what to pass and where it comes from. Nothing could be removed without losing information.

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?

For a single-parameter read-only lookup with no output schema, the description covers both the input provenance and the return content, including the conditional failure detail. It falls just short of full completeness by omitting pending/unknown-run behavior, but nothing essential to a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents run_id at 100% coverage, but only as 'Run id.' The description adds provenance the schema lacks, tying the value to ids returned by run_test or run_group, which tells an agent where to source the argument instead of guessing.

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 the resource and what it yields: a run's status, plus step and failure reason when a test failed. The verb is implicit ('get' is only in the name), but the returned content is specific enough that an agent can distinguish this from run_test/run_group, which produce run ids rather than report outcomes.

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?

'Pass the run id run_test or run_group returned' gives a real workflow cue: this tool is the follow-up to starting a run, and the id comes from those two siblings. However, there is no explicit statement of when not to use it or what to do for multi-run or list-style lookups, so guidance is implied rather than complete.

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