Skip to main content
Glama

Open a draft fix PR for an error issue

create_fix_pr

Open your fix for an issue as a draft PR in the app's repo, with Fixes <short id> so the issue resolves when it ships. Send patches (git diff) per file. No build, CI or .github changes. Needs "Let MCP keys open pull requests".

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": {
      "issue_id": "<issue_id>",
      "root_cause": "<root_cause>",
      "summary": "<summary>",
      "files": "<files>"
    },
    "name": "create_fix_pr"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
titleNo
summaryYesWhat the change does
issue_idYes
tests_runNo
root_causeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive, but the description adds real behavior: the result is a *draft* PR, the `Fixes <short id>` trailer auto-closes the issue on ship, certain paths (build, CI, .github) are rejected, and an account-level permission must be enabled. What it omits is what comes back (PR URL/number) and whether a retry creates a duplicate PR, which matters for a non-idempotent tool.

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?

Three tight sentences, front-loaded with the action and the issue-resolution mechanism before constraints. The trailing permission line is slightly cryptic in wording but earns its place as a precondition.

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 mutating, open-world tool with no output schema and thin parameter coverage, the description covers the headline behavior, content restrictions, and a prerequisite, but leaves key inputs (root_cause, summary, tests_run) and the response shape undocumented.

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

Parameters3/5

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

Schema description coverage is only 17%, so the description must compensate, and it partially does by tying the patch format (git diff, preferred smaller) to files and explaining the `Fixes <short id>` linkage to issue_id. It says nothing about root_cause, summary, title, or tests_run, leaving four required/optional inputs without meaning in either place.

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 and resource: open the fix for an issue as a draft PR in the app's repo. It also describes the linking mechanism (`Fixes <short id>`) that makes the issue resolve on ship. It does not explicitly distinguish itself from create_pull_request or start_fix_run, so a 4 rather than 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?

Implies the usage context (after diagnosing an issue, ship your fix as a draft PR) and lists hard constraints: send per-file patches, no build/CI/.github changes, and the 'Let MCP keys open pull requests' setting must be enabled. It never says when to prefer this over the sibling create_pull_request or the start_fix_run workflow, so guidance is implied rather than explicit.

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