Skip to main content
Glama

Progress of an AI fix run

get_fix_run
Read-only

A fix run's status, root cause, plan, files, tests, cost so far, and its pull request.

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_fix_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context by disclosing that the response includes live, partial state ('status', 'cost so far'), implying repeated polling is expected. It does not mention auth requirements, error behavior for an unknown run id, or freshness/latency.

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?

One compact sentence with no filler, and the most load-bearing elements (status, root cause, pull request) appear early. It is a noun fragment rather than a clause, which costs a little immediate legibility but wastes no space.

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?

With no output schema, the description does the right thing by enumerating the returned fields, which is the main completeness requirement here. It still leaves the agent without guidance on the run_id source, polling cadence, or failure modes for a tool whose whole purpose is repeated status checks.

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?

The single run_id parameter has 0% schema description coverage; the schema only supplies a UUID format and pattern. The description never mentions run_id, where it comes from (presumably returned by start_fix_run), or what happens if it is stale or unknown, so it adds no meaning beyond the structured fields.

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 the specific resource (a single fix run) and enumerates the payload it surfaces — status, root cause, plan, files, tests, cost, pull request — which lets an agent distinguish it from start_fix_run and create_fix_pr. It omits a verb, so the read-only retrieval framing comes from the name rather than the prose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no exclusion, and no alternative named. The phrase 'cost so far' hints that the tool is meant to be polled for in-flight runs, but that inference is left entirely to the agent, and nothing says when to prefer this over get_pull_request_status or start_fix_run.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources