devops-wrangler

ado_comments

Add or list comments on Azure DevOps work items with markdown support for formatting.

Instructions

Manage work item comments.

Actions:

add: Add comment to work item (requires: id, text)
list: List comments on work item (requires: id, optional: limit)

Markdown Support: Azure DevOps comments support full markdown formatting including bold, italic, code, lists, headers, links, and code blocks.

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": {
      "action": "<action>",
      "id": "<id>"
    },
    "name": "ado_comments"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Work item ID
`text`	No	Comment text with markdown support (for add)
`limit`	No	Max comments to return (for list)
`action`	Yes	Action to perform

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses markdown support and per-action required parameters, but stops short of describing side effects, permissions, return values, or error behavior. It adds some context beyond the schema, but not complete safety/behavioral disclosure.

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 concise and well-structured: a one-line summary, a bullet list of actions, and a note on markdown. No fluff.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-action tool, the description covers the actions and required inputs. However, it lacks details on list behavior (ordering, pagination), response format, and any error or authorization context. Without an output schema, more explanation of return values would improve completeness.

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 covers all 4 parameters with descriptions. The description repeats which parameters are needed for each action, which is useful but not additive beyond the schema. 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?

The description identifies the resource (work item comments) and lists specific actions (add, list), distinguishing it from sibling tools that manage other aspects of Azure DevOps. 'Manage' is slightly generic, but the action list provides clear purpose.

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

Usage Guidelines3/5

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

The description implies usage for managing comments but doesn't offer explicit guidance on when to use this versus alternatives or when not to use. It gives action-specific requirements but no exclusions or alternative tool references.

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

Deploy Server