Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Update work item

devops_work_item_update
Destructive

Update specific fields on an Azure DevOps work item by ID using add, replace, or remove operations; optionally validate changes with a dry run before saving.

Instructions

Update fields on a work item by ID.

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": {
      "work_item_id": "<work_item_id>",
      "updates": "<updates>"
    },
    "name": "devops_work_item_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYesList of field updates to apply. Each entry must have: 'op' (one of 'add', 'replace', 'remove'; defaults to 'add'), 'name' (field reference name, e.g. 'System.Title'), and 'value' (required for 'add'/'replace', omit for 'remove').
work_item_idYesThe numeric work item ID to update.
validate_onlyNoIf True, validate the input against system rules without saving the work item (dry run).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered structurally. The description adds nothing on top of that: it does not say that listed field values are overwritten, what happens to fields not included in the updates list, or that changes are not reversible. For a destructive mutation the description is essentially silent on behavior.

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?

It is a single short, front-loaded sentence with no filler or redundancy in phrasing. Its brevity works against it in other dimensions, but as a structural matter nothing is wasted.

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?

An output schema exists and annotations cover the safety profile, and the input schema fully documents all three parameters, so the description need not repeat those. Still, for a destructive, multi-field mutation tool the description leaves out the one thing structured fields cannot convey: how partial updates behave and what guarantees the caller has, making it only minimally adequate.

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 schema itself documents the updates array structure, the work_item_id, and the validate_only dry-run flag in detail. The description only echoes the ID aspect ('by ID') and adds no meaning beyond what the schema already provides, so the baseline 3 applies.

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

Purpose3/5

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

The sentence names a verb (update) and a resource (fields on a work item) plus an identifier, so the basic operation is legible. However, it is very close to a restatement of the tool name and title, and it gives no signal for distinguishing general field updates from the several sibling update tools (comment, link, artifact-link) that act on the same work item.

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 when-to-use guidance at all: no statement that this is for general field edits as opposed to comment/link/artifact updates, no prerequisites or permission notes, and no mention that validate_only exists as a dry-run path. The agent must infer routing entirely from sibling names.

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