Skip to main content
Glama

get_run

Retrieves the current state of a Codex DPH run, including whether it is awaiting review so Codex can inspect artifacts and diffs.

Instructions

Get current state. awaiting_review requires Codex to inspect artifacts and diff.

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

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for a read tool. It discloses one behavioral trait (the awaiting_review state implies a required follow-up inspection) but says nothing about error behavior for invalid run_ids, whether the state is live or cached, or what fields come back.

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?

Two short sentences, front-loaded with the core action, with no filler. The second sentence is somewhat cryptic but at least implies a workflow branch rather than padding.

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 output schema, no annotations, one entirely undocumented parameter, and no statement of what state is returned, an agent cannot confidently predict the response or handle the awaiting_review case. The definition is too thin for the tool's role in a review workflow.

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 single run_id parameter is never mentioned or explained – no format, no source (where does the agent obtain a run_id?), no constraints. The description does nothing to compensate for the documentation gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get current state" names a retrieval action but never says state of what – the run resource is only inferable from the tool name. It is marginally more specific than a tautology but still vague about scope (a single run's status vs. full details).

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?

The clause about awaiting_review requiring inspection of artifacts and diff implicitly routes the agent toward get_artifacts/get_diff siblings, which is useful conditional guidance. However, it never states when to call get_run itself versus list_runs or read_events, leaving the main usage decision to inference.

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