Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Add or remove work item link

devops_work_item_link_update
Destructive

Add or remove a relation link between two work items; use op='add' or op='remove', and change a link type by removing then adding it.

Instructions

Add or remove a relation link between two work items. Use op='add' (default) to create a new link, op='remove' to delete an existing one. To change a link type, call remove then add.

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_to_id": "<link_to_id>"
    },
    "name": "devops_work_item_link_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNoOperation to perform: 'add' (default) to create the link, 'remove' to delete it.add
commentNoOptional comment to attach to the link. Only used when op='add'.
link_typeNoType of link. One of: 'parent', 'child', 'related', 'duplicate', 'duplicate of', 'successor', 'predecessor', 'tested by', 'tests', 'affects', 'affected by'. Defaults to 'related'.related
link_to_idYesThe numeric ID of the work item to link to or unlink from.
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.8/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 agent knows this mutates and can delete data. The description adds the useful detail that changing a link type is a non-atomic remove-then-add sequence, which has real consequences. However, it says nothing about permissions, error behavior when unlinking a nonexistent link, or the effects of validate_only beyond what the schema already states.

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?

Three short sentences, front-loaded with the core action and followed by the two operational rules an agent needs. No filler, no restatement of the title, and the most important constraint (remove-then-add to change type) is placed last where it is easy to find.

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?

The tool has six parameters, an output schema, and full schema coverage; the description covers the mutation semantics and the non-obvious type-change workflow. The only gap is that it does not mention prerequisites or permission requirements for a destructive operation, which the annotations signal but do not explain.

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 every parameter including op, link_type, comment, and validate_only is already fully documented in the schema. The description reinforces the op default and the remove-then-add pattern but adds no format, ID, or type semantics beyond the structured fields.

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 (add/remove) and resource (relation link between two work items), which is concrete and distinguishable from a generic work-item update. It does not explicitly contrast itself with the sibling devops_work_item_artifact_link_update, so the relation-vs-artifact distinction is only implied by the word 'relation'.

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

Usage Guidelines4/5

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

Gives clear operating guidance: op='add' by default, op='remove' to delete, and the explicit recipe for changing a link type (remove then add). It stops short of stating when a link should be used instead of a sibling tool such as the artifact-link variant, so no explicit alternative routing is provided.

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