Skip to main content
Glama

get_run

Retrieve a run's current status, terminal reason, or measured result using its run ID.

Instructions

Get current status, terminal reason or measured result by run ID.

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_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It implicitly claims read-only behavior and usefully signals that the payload varies with run lifecycle (status while live, terminal reason when finished, measured result otherwise), which is genuine behavioral context beyond a bare 'get'. It does not say what is returned for an in-progress run (null result? partial?), whether runs are retained/expire, or whether an unknown ID errors or returns empty.

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?

One sentence, front-loaded with the verb and resource, zero filler. Every clause (status, terminal reason, measured result) carries distinct information about what can come back.

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 with no output schema and no annotations, the description covers the essentials of what is returned but leaves lifecycle edge cases and ID provenance unspecified. Adequate to invoke correctly, thin on what to expect from the response.

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

Parameters2/5

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

Schema description coverage is 0% and there is a single parameter, so the description must compensate. 'By run ID' only restates the parameter name run_id; it gives no format, provenance, or how to obtain a valid ID (presumably from list_runs). The agent learns nothing it could not read from the schema.

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?

States a specific verb (Get) and resource (run) plus the three things it can return: status, terminal reason, or measured result, keyed by run ID. That is concrete and readable at a glance, and the ID-based retrieval distinguishes it from the sibling list_runs. It doesn't explicitly name a counterpart, but the resource/scope is unambiguous.

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 only implied: 'by run ID' tells the agent this is single-run lookup rather than enumeration, which implicitly routes list-style needs to list_runs. There is no explicit when-to-use statement, no when-not, and no mention of alternatives such as describe or compare, so an agent must infer selection from the name alone.

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