Skip to main content
Glama

run_get

Read-onlyIdempotent

Read a run's identity, last confirmed state, failure count, and accounting data without credentials, enabling monitoring and recovery.

Instructions

Read job identity, last confirmed state, failure count and accounting independently of credentials.

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": "run_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds two traits not in the structured data: it works without credentials, and the state reported is "last confirmed" rather than necessarily live — a meaningful freshness caveat for an agent reasoning over the result. It stops short of describing error behavior for an unknown 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?

A single dense sentence that front-loads the payload fields before the credential caveat. Nothing is padded and no sentence is wasted.

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?

An output schema exists, so return-value explanation is correctly omitted, and the annotations plus the credential/freshness notes give an agent most of what it needs. The one real hole is the undocumented run_id, which leaves the call signature underspecified relative to the otherwise rich behavioral framing.

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 the description never mentions run_id at all — no format, source, or example value. With a sub-50% coverage parameter this text is expected to compensate, and the self-explanatory name is the only reason this is not a 1.

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?

Names a specific verb ("Read") and enumerates the exact fields returned: job identity, last confirmed state, failure count, and accounting. That is far more concrete than a tautological restatement of run_get, though it never distinguishes itself from siblings like check_run or run_log, which plausibly touch the same run object.

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: the phrase "independently of credentials" suggests it is the right choice when authentication is unavailable, but no explicit when-to-use statement, prerequisite, or named alternative is given. An agent must infer the selection rule against check_run and run_log rather than being told it.

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