Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Restore deleted work item

devops_work_item_undelete

Restore a deleted work item from the Azure DevOps Recycle Bin by numeric ID; only items deleted without the destroy flag can be recovered.

Instructions

Restore a work item from the Recycle Bin by ID. Only works for items deleted without the destroy flag.

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_undelete"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_item_idYesThe numeric ID of the deleted work item to restore.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured fields. The description adds one real behavioral trait beyond that — the destroy-flag restriction — but says nothing about permissions, whether a restored item returns to its original fields/links, or what the state transition looks like.

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 short sentences with zero filler; the operation and its precondition are both front-loaded and each sentence earns its place.

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 one-parameter restore tool with an output schema and safety annotations, purpose plus the destroy-flag caveat covers what an agent needs to call it correctly. It could go slightly further by clarifying how an agent can tell whether an item was destroyed versus soft-deleted.

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% with a single integer parameter that the schema already documents as 'the numeric ID of the deleted work item to restore'. The description's 'by ID' adds no syntax, format, or sourcing detail beyond that, so baseline 3 applies.

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?

States a specific verb and resource ('Restore a work item') plus the source location ('from the Recycle Bin') and the keying parameter ('by ID'). The 'undelete' semantics are unambiguous and clearly separated from the sibling delete tool.

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 sentence 'Only works for items deleted without the destroy flag' is an explicit when-it-will-fail precondition, which is genuine usage guidance. It stops short of naming an alternative recovery path for destroyed items, so it is not a full when-to-use vs alternative statement.

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