Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Add or remove work item artifact link

devops_work_item_artifact_link_update
Destructive

Attach or detach Pull Request, build, commit, branch, changeset, or versioned item links to Azure DevOps work items by specifying work item ID, link type, and artifact ID.

Instructions

Add or remove an artifact link (Pull Request, Build, Commit, Branch, Changeset, Versioned Item) on a work item. Use op='add' (default) to attach, op='remove' to detach. The artifact_id format depends on link_type (see parameter doc).

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>",
      "link_type": "<link_type>",
      "artifact_id": "<artifact_id>"
    },
    "name": "devops_work_item_artifact_link_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNoOperation to perform: 'add' (default) to attach the artifact link, 'remove' to detach it.add
commentNoOptional comment to attach to the link. Only used when op='add'.
link_typeYesSupported: 'Pull Request', 'Build', 'Found in build', 'Integrated in build', 'Commit', 'Branch', 'Changeset', 'Versioned Item'.
artifact_idYesArtifact identifier — format depends on link_type: Git-based (Pull Request / Commit / Branch / Versioned Item): '{project_id}/{repo_id}/{detail}', where project_id and repo_id are GUIDs (use devops_repository_get to resolve names), and detail is the PR number, commit SHA, branch name, or file path respectively. Build / Found in build / Integrated in build: '{build_id}'. Changeset: '{changeset_id}'.
work_item_idYesThe numeric ID of the work item to modify.
validate_onlyNoIf True, validate without saving (dry run).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is carried by structured data. The description adds that 'remove' detaches an existing link, which aligns with the destructive hint, but says nothing about irreversibility, permissions, or rate limits. The dry-run capability exists in the schema but is not surfaced in the description.

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?

Three short sentences with the action and scope front-loaded, then the operation switch, then the format caveat. Little waste, though the pointer to 'parameter doc' is marginally redundant given the schema is the parameter doc.

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

Completeness4/5

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

With full schema coverage, a present output schema, and annotations covering the mutation/destructive profile, the description supplies what an agent needs to call this correctly. Only missing element is explicit routing against the sibling link tool, which is a minor gap for a mutation of this complexity.

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%, so the schema already documents op, link_type, artifact_id formats, comment, and validate_only in detail. The description only restates the op default and defers artifact_id formatting to the parameter doc ('see parameter doc'), adding no meaning beyond the schema.

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?

States a specific verb pair (add/remove) and resource (artifact link) on a work item, and enumerates the artifact kinds it handles (Pull Request, Build, Commit, Branch, Changeset, Versioned Item). The artifact enumeration implicitly separates it from the work-item-to-work-item link sibling, though that sibling is never named explicitly.

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?

Explains the two modes clearly — op='add' is the default to attach, op='remove' detaches — which gives real selection guidance between the tool's own operations. It offers no guidance on when to use this versus devops_work_item_link_update or other link-related siblings, so alternative selection is left to inference.

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