Skip to main content
Glama

run_action

DestructiveIdempotent

Manage queue actions for a single run: reconcile state, collect results, or cancel the job without consuming submission attempts.

Instructions

Queue reconcile, collect or cancel for one run. These actions do not consume submission attempts.

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>",
      "action": "<action>",
      "revision": "<revision>",
      "op_id": "<op_id>"
    },
    "name": "run_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
actionYes
run_idYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is partly covered. The description adds genuinely new context — that these actions are free with respect to submission attempts — but it doesn't say which action is the destructive one (presumably cancel), what gets destroyed, or whether cancel is reversible.

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, the scope constraint front-loaded and the cost caveat second; nothing is padding and both sentences carry information.

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?

An output schema exists, so return values need not be described, and the destructive/idempotent profile is annotated. Against that, a four-parameter mutation tool with zero schema descriptions and no explanation of revision or op_id is under-specified for an agent to call confidently.

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% across four required parameters, so the description carries the full burden and mostly fails. It implicitly maps 'reconcile, collect or cancel' to the action enum and 'one run' to run_id, but revision and op_id are never explained — op_id especially, given idempotentHint=true, looks like an idempotency key the agent must generate correctly.

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 names specific verbs (reconcile, collect, cancel) tied to a concrete resource scope ('for one run'), so an agent can tell this is a per-run action dispatcher rather than a status reader like check_run or run_get. The verbs 'reconcile' and 'collect' are domain jargon that isn't unpacked, which keeps it from a 5.

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 second sentence gives a real selection hint: these actions do not consume submission attempts, implying they are the cheap alternative to run_submit for housekeeping. However, it never states when to pick reconcile vs collect vs cancel, nor names an alternative tool explicitly.

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