Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Update pull request thread status

devops_pull_request_update_thread
Destructive

Update the status of a pull request comment thread in Azure DevOps to mark it active, fixed, resolved, wontfix, closed, or pending.

Instructions

Update the status of a comment thread.

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": {
      "repository_id": "<repository_id>",
      "pull_request_id": "<pull_request_id>",
      "thread_id": "<thread_id>",
      "status": "<status>"
    },
    "name": "devops_pull_request_update_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesNew thread status (1=Active, 2=Fixed or Resolved, 3=WontFix, 4=Closed, 6=Pending).
thread_idYesThread ID to update.
repository_idYesRepository name or ID.
pull_request_idYesPull request ID.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare a non-read-only, destructive mutation. The description adds nothing beyond that: it does not explain allowed status transitions, whether resolving or closing a thread can be undone, what permissions are required, or what the destructive effect actually is.

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 a single concise sentence with the action front-loaded. It is efficient, though the brevity leaves real gaps rather than being optimally informative.

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 a fully described input schema, an output schema, and annotations carrying the mutation/destructive profile, the definition is minimally sufficient. However, for a destructive thread-status mutation it should clarify how it differs from updating a comment and what status changes imply.

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%, and the status enum is fully documented in the schema. The description adds no additional meaning about repository_id, pull_request_id, thread_id, or status values, so the baseline score of 3 is appropriate.

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 gives a specific verb and resource: updating a comment thread's status. It is clear what the tool does, but it does not distinguish this from sibling operations such as devops_pull_request_update_comment or explain which thread fields are affected beyond status.

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 explicit guidance on when to use this tool versus devops_pull_request_update_comment or the list/reply thread tools. The name and description imply status updates only, but the agent receives no conditions, prerequisites, or alternatives.

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