ado-workflows-mcp

by grimlor

Overview Schema Source Related Servers Discussions Admin

Python

Local

complete_pull_request

Merge a pull request with configurable merge strategy, branch deletion, and policy bypass options.

Instructions

Complete (merge) a PR with configurable merge strategy.

Args: pr_url_or_id: A full PR URL or numeric PR ID. merge_strategy: One of: squash, noFastForward, rebase, rebaseMerge. delete_source_branch: Whether to delete the source branch after merge. transition_work_items: Whether to transition linked work items. merge_commit_message: Optional merge commit message. bypass_policy: Whether to bypass branch policies. bypass_reason: Required when bypass_policy is True. working_directory: Optional path for context resolution.

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": {
      "pr_url_or_id": "<pr_url_or_id>"
    },
    "name": "complete_pull_request"
  }
}

Input Schema

Name	Required	Default
`pr_url_or_id`	Yes
`merge_strategy`	No	squash
`delete_source_branch`	No
`transition_work_items`	No
`merge_commit_message`	No
`bypass_policy`	No
`bypass_reason`	No
`working_directory`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.12.0May 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations exist, so the description carries full burden. It discloses some behavioral traits like configurable merge strategy and options to delete source branch or bypass policies, but lacks details on side effects (e.g., commit creation, conflict handling) and overall impact.

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?

The description is concise with a clear first sentence followed by a parameter list. Each line earns its place; no redundancy.

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?

Given 8 parameters and a merge operation, the description adequately documents each parameter but lacks overall behavioral context (e.g., effect on repository, authorization needs). An output schema exists but its content is unknown.

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

Parameters4/5

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

Schema description coverage is 0%, but the description provides meaningful comments for each parameter (e.g., enum values for merge_strategy, condition for bypass_reason). This compensates well for the schema gap, though some defaults are already in schema.

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?

The description clearly states 'Complete (merge) a PR with configurable merge strategy.' This is a specific verb+resource combination that distinguishes it from siblings like create, abandon, or update PR tools.

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?

No explicit guidance on when to use this tool versus alternatives such as update_pull_request or abandon_pull_request. The description only lists parameters without context on prerequisites or exclusions.

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

Deploy Server