Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Delete work item

devops_work_item_delete
Destructive

Delete an Azure DevOps work item by ID, moving it to the Recycle Bin for restoration or permanently destroying it when destroy is true.

Instructions

Delete a work item by ID. By default the item is sent to the Recycle Bin and can be restored. Set destroy=True to permanently destroy the item — WARNING: this is irreversible.

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>"
    },
    "name": "devops_work_item_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
destroyNoIf True, permanently destroys the work item (requires 'Permanently delete work items' permission in Project Settings → Security; if not enabled, the server returns 404). WARNING: permanent destruction cannot be undone. Defaults to False (moves to Recycle Bin).
work_item_idYesThe numeric ID of the work item to delete.

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 destructive profile is structured data. The description still adds genuinely useful behavior: the default path is recoverable from the Recycle Bin while destroy=True is irreversible, which is not derivable from the hints alone. It omits side effects such as whether child comments, links, or attachments are also removed.

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?

Two sentences with zero waste. The safe default is stated first and the irreversible mode with its warning comes second, which is the correct ordering for a destructive tool.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. Both operating modes are covered. The remaining gap is scope of deletion (whether related artifacts are affected) and where the item lands relative to the undelete sibling.

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%, and the schema already documents destroy's default, its permission requirement, the 404 behavior when the permission is absent, and the irreversibility. The description restates the destroy semantics without adding syntax or format detail beyond the schema, so baseline 3 applies.

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 and resource ('Delete a work item by ID') and immediately qualifies the two deletion modes, so the agent knows exactly what operation it is. It does not name sibling tools such as devops_work_item_undelete, which handles the restore path, so differentiation is inferred rather than stated.

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?

The description clearly explains the selection rule between the two modes: default is a recoverable Recycle Bin delete, destroy=True is permanent. It gives no explicit guidance on when to prefer one over the other in workflow terms, nor does it point to the undelete sibling for recovery.

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