arcade-azure-devops-mcp

AzureDevops_UpdateWorkItem

AzureDevops_UpdateWorkItem

Modify an existing Azure DevOps work item: update its title, description, state, priority, or assignee to keep information accurate.

Instructions

Update an existing work item.

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": {
      "project": "<project>",
      "work_item_id": "<work_item_id>"
    },
    "name": "AzureDevops_UpdateWorkItem"
  }
}

Input Schema

Name	Required	Description
`state`	No	New state
`title`	No	New title
`project`	Yes	Project name or ID
`priority`	No	New priority
`assigned_to`	No	New assignee
`description`	No	New description
`work_item_id`	Yes	Work item ID to update

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description alone must disclose behavior. It only says 'update an existing work item' without clarifying whether the operation is a partial update (only provided fields change) or a full replacement, how errors are handled (e.g., nonexistent work item), or permission requirements. This is a significant gap for a mutating tool.

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 a single concise sentence with no redundant wording or filler. It is immediately clear and front-loaded, earning a high score for structure despite its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, no annotations, and no output schema, the description is under-specified. It does not explain the return value or success condition, whether the update is partial, or any side effects. The minimal one-liner is insufficient for an agent to fully understand the tool's behavior, especially compared to sibling tools that provide more context.

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?

All 7 parameters are already described in the input schema, satisfying schema_description_coverage at 100%. The description itself adds no additional meaning to parameters, but per the rubric, a baseline of 3 is appropriate when the schema already documents parameters. No extra syntax or behavior details are provided in the description.

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 states a specific action ('update') on a specific resource ('existing work item'), clearly indicating it modifies an existing item rather than creating a new one. However, it does not differentiate from sibling 'AddWorkItemComment' which also modifies a work item, but the core purpose is still unambiguous.

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

Usage Guidelines3/5

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

The description does not explicitly state when to choose this tool over alternatives like 'CreateWorkItem' or 'GetWorkItem'. The usage context is implied by the word 'update' and the required 'work_item_id' parameter, but there is no explicit guidance on exclusions or alternatives, making it minimally adequate.

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