Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Create or update pull request

devops_pull_request_write
Destructive

Create, update, and manage Azure DevOps pull requests, including adding or removing reviewers and casting votes.

Instructions

Write operations for pull requests. Use the action parameter to create or update pull requests, add or remove reviewers, or cast the authenticated user's vote.

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": {
      "action": "<action>"
    },
    "name": "devops_pull_request_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
voteNoVote to cast: Approved, ApprovedWithSuggestions, NoVote, WaitingForAuthor, or Rejected.
titleNoPull request title. Required for create; optional for update.
actionYesAction to perform: create, update, update_reviewers, or vote.
labelsNoLabel names. Used for create and update.
statusNoNew status for update: Active or Abandoned.
is_draftNoWhether the pull request is a draft. Used for create and update.
work_itemsNoSpace-separated work item IDs to associate. Used for create.
descriptionNoPull request description. Used for create and update.
reviewer_idsNoReviewer IDs. Required for update_reviewers.
auto_completeNoSet or clear autocomplete. Used for update.
bypass_policyNoBypass branch policies on autocomplete. Requires bypass_reason.
bypass_reasonNoReason for bypassing branch policies.
repository_idNoRepository name or ID. Required for all actions.
merge_strategyNoMerge strategy for autocomplete. Used for update.
pull_request_idNoPull request ID. Required for update, update_reviewers, and vote.
reviewer_actionNoReviewer action: add or remove. Required for update_reviewers.
source_ref_nameNoSource branch ref for create, for example refs/heads/feature-branch.
target_ref_nameNoTarget branch ref for create or update, for example refs/heads/main.
delete_source_branchNoDelete source branch on autocomplete. Used for update.
merge_commit_messageNoCommit message for autocomplete. Used for update.
transition_work_itemsNoTransition work items on autocomplete. Used for update.
fork_source_repository_idNoFork source repository ID. Used for create.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already disclose readOnlyHint=false and destructiveHint=true, and the description reinforces that these are write operations. Beyond that, it does not add detail about permissions, irreversibility, or which actions are destructive, so it adds only modest behavioral context beyond the annotations.

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?

The description is two short sentences with the resource and action scope front-loaded. Every sentence contributes directly to understanding what the tool does and how the action parameter drives it.

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?

Given the rich schema with full parameter descriptions, existing annotations, and an output schema, the description provides enough context to identify this as the pull-request mutation tool and to invoke it through the action parameter. A complex 22-parameter multi-action tool could benefit from slightly more action-specific orientation, but the structured fields carry most of the detail.

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 the schema already documents the 22 parameters and their action-specific requirements. The description adds a high-level mapping from action to create/update/reviewer/vote operations, but no additional parameter syntax or constraints beyond the schema.

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 resource (pull requests) and enumerates the operations: create, update, add/remove reviewers, and vote. It is clear what the tool does, though it does not explicitly contrast itself with sibling pull-request comment/thread write 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?

It explicitly tells the agent to use the action parameter for the supported pull-request write operations. It gives clear usage context but does not state when to use alternatives or when not to use this tool.

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