Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Delete work item comment

devops_work_item_comment_delete
Destructive

Delete a comment from an Azure DevOps work item by specifying the work item ID and comment ID.

Instructions

Delete a comment from a work item.

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

Input Schema

NameRequiredDescriptionDefault
comment_idYesThe numeric ID of the comment to delete.
work_item_idYesThe numeric work item ID.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether the deletion is permanent or soft, whether replies/threaded comments are affected, or what happens if the comment ID is invalid. For an irreversible mutation this is a real gap even with the lower annotated bar.

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?

A single short sentence with zero waste and the action front-loaded. It is efficient, but the brevity here reflects under-specification rather than disciplined editing.

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

Completeness2/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 not be explained, and annotations carry the destructive flag. However, for a permanently destructive delete on a nested resource, the definition omits irreversibility, permission needs, and any effect on surrounding comment threads — the agent has just enough to identify the operation, not enough to invoke it confidently.

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 coverage is 100% with two required integer parameters, each already documented in the schema as the numeric comment ID and the numeric work item ID. The description adds no meaning beyond that, which is acceptable given the schema does the work, but it earns only the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially a restatement of the tool name and title: "Delete a comment from a work item." It names the verb and resource, but adds no scope, no distinction from siblings such as devops_pull_request_delete_comment or devops_work_item_comment_update, and no clue about what a comment is here.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all. It does not say when to delete versus update a comment (devops_work_item_comment_update) or how it differs from deleting a comment on a pull request, and it states no prerequisites such as required permissions or whether the comment must exist.

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