start-work

Open pull request

open_pull_request

Open a pull request that closes a ticket, moves it to review, and comments with the PR link after your branch is pushed and tests pass; humans handle merge.

Instructions

After the branch is pushed and tests pass: open a PR that closes the ticket, move the ticket to in review, and leave a comment linking the PR. A human reviews before merge.

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": {
      "number": "<number>",
      "branch": "<branch>",
      "summary": "<summary>",
      "testing": "<testing>"
    },
    "name": "open_pull_request"
  }
}

Input Schema

Name	Required	Description
`base`	No	Target branch (default: the repo's default branch).
`draft`	No	Open as a draft (use when acceptance criteria aren't all met).
`notes`	No	Assumptions, open questions, anything the reviewer should look at closely.
`branch`	Yes	The pushed branch.
`number`	Yes	The ticket number.
`summary`	Yes	What changed and why, for the reviewer.
`testing`	Yes	How it was verified: tests added or run, manual checks.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are supplied, so the description must carry behavioral disclosure. It discloses the multi-step side effects (ticket closure, status change, comment) and the human-review gate, though it omits permissions, idempotency, and failure behavior.

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 sentences, front-loaded with the prerequisite and action, with no redundant wording. Every clause adds workflow or side-effect information.

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?

For a seven-parameter mutation with no annotations and no output schema, the description covers the key workflow and side effects. It leaves out return-value expectations and error handling, but the core invocation context is present.

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 100%, so all seven parameters are already documented in the schema. The description adds workflow context but no additional parameter-level meaning beyond what the schema provides.

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

Purpose5/5

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

Opens a pull request and explicitly names the follow-on effects: closing the ticket, moving it to in review, and commenting with the PR link. The verb and resource are specific, and the workflow context distinguishes it from the ticket-only sibling tools.

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

Usage Guidelines4/5

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

States the prerequisite clearly: use after the branch is pushed and tests pass. It does not name alternatives or when not to use, but the gating condition is explicit.

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

Deploy Server