devops-wrangler

ado_delete_item

Delete Azure DevOps work items by ID. Default moves to recycle bin; use permanent=true for permanent deletion.

Instructions

Delete a work item (moves to recycle bin by default, use permanent=true for hard delete)

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Work item ID to delete
`permanent`	No	Permanently delete (DANGER: cannot be undone)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 9, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It does state the default move-to-recycle-bin behavior and mentions permanent hard delete. However, it does not mention permissions, response format, or other side effects, leaving some gaps for a destructive operation.

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 one compact sentence that front-loads the verb and resource, then clarifies the default and option. No wasted words.

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?

For a simple two-parameter tool with no output schema, the description covers the essential behavior: what deleting does by default and how to make it permanent. It could mention return/error behavior, but it is sufficiently complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, giving a baseline of 3. The description adds value by explaining the default behavior (recycle bin) and how to trigger hard delete with 'permanent=true', which goes beyond the schema's field descriptions.

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 ('Delete') and resource ('a work item'), clearly distinguishing it from sibling tools like update/create/query. It also explains the default recycle-bin behavior and the permanent option, adding useful scope.

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 provides clear context on when to use it: deleting a work item, with guidance on the default soft-delete vs hard-delete via 'permanent=true'. It does not explicitly say when not to use it or name alternatives, but for a delete operation this is not strictly necessary.

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

Deploy Server