ado-mcp

ado_update_work_item

Modify fields of an existing Azure DevOps work item using its ID and a map of field reference names to new values.

Instructions

Update a work item's fields.

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": {
      "id": "<id>",
      "fields": "<fields>"
    },
    "name": "ado_update_work_item"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Work item ID
`fields`	Yes	Field map keyed by reference name, e.g. {"System.Title":"Fix bug","System.State":"Active"}
`project`	No	Project name or ID (defaults to ADO_DEFAULT_PROJECT)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It only states 'Update a work item's fields', which implies mutation, but does not explain side effects, return values, error states, permissions, or whether the update is partial or full replacement. Significant transparency gaps exist.

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 extremely concise with a single sentence that directly states the purpose. It avoids unnecessary words and is front-loaded. However, it could include brief usage context without becoming verbose.

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?

The tool operates in a rich ecosystem of sibling tools for work items, yet the description does not explain how this tool fits (e.g., that it updates an existing work item partially). With no output schema, the return behavior is completely opaque. The description is too minimal to be fully actionable in 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?

Schema coverage is 100% with each parameter described adequately (id as integer, fields as object with example, project as optional string). The description adds no additional semantic context beyond the schema. Baseline score of 3 is appropriate given high coverage.

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 tool name 'ado_update_work_item' and description 'Update a work item's fields.' clearly indicate the verb (update) and resource (work item fields). It distinguishes from sibling tools like create, delete, and get which have different verbs. However, it could be more explicit about updating an existing work item, but it's still clear enough.

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 guidance is provided on when to use this tool versus alternatives like creating, deleting, or querying work items. It does not mention prerequisites, such as needing the work item ID or whether partial updates are allowed. No exclusions or when-not-to-use scenarios are described.

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

Deploy Server