devops-wrangler

ado_link_item

Link Azure DevOps work items to related pull requests, commits, branches, or other work items to track dependencies and code changes.

Instructions

Link a work item to another work item, pull request, commit, or branch

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>",
      "linkType": "<linkType>",
      "target": "<target>"
    },
    "name": "ado_link_item"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Work item ID
`target`	Yes	Target work item ID, PR number, commit SHA, or branch name
`comment`	No	Link comment
`linkType`	Yes	Type of link to create

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 9, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral implications, but it only states the action itself. It does not mention that linking is a mutating operation, whether it is reversible, permission requirements, or any side effects on existing links. This leaves significant uncertainty about the tool's impact.

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, compact sentence that immediately states the action and scope. There is no redundant wording or repetition of schema information, making it highly efficient.

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?

The tool is relatively simple and the schema documents the parameters well, but the description lacks practical context such as examples, the relationship between linkType and target formats, or any conditions for successful linking. It is adequate for a basic understanding but does not fully equip an agent to use the tool correctly in nuanced cases.

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 four parameters are fully described in the schema, so the baseline is 3. The description does not add any extra meaning beyond the schema, such as explaining how linkType constrains the target format or how comment is used in the link context.

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

Purpose5/5

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

The description uses a specific verb ('Link') and clearly identifies the resource ('a work item') and the range of valid targets ('another work item, pull request, commit, or branch'). This distinguishes it from sibling tools like create_items or update_item, which perform different operations.

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 implies the tool's purpose (creating links) but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The context is clear enough for basic understanding, but there is no directional advice for an AI agent.

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

Deploy Server