Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

List work item comments

devops_work_item_comment_list
Read-only

Retrieve comments from an Azure DevOps work item, with options to cap the number returned and choose HTML or markdown format for review.

Instructions

List comments on a work item. Returns up to top comments (default 50).

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

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of comments to return. Defaults to 50.
formatNoResponse format: 'html' (default) or 'markdown'.html
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a real behavioral fact beyond that — a result cap with a default of 50 — but says nothing about ordering, pagination beyond the cap, or what happens when more comments exist than `top`.

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?

Two short sentences, front-loaded with the purpose and free of filler. The second sentence is partially redundant with the schema's default value for `top`, which keeps it from a 5.

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?

An output schema exists, so return-value explanation is rightly omitted, and annotations cover the read-only profile. For a simple three-parameter list tool it is mostly adequate, but an agent still cannot tell whether the 50-item cap is a hard truncation, how to page past it, or how results are ordered.

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%, so all three parameters are already documented in structured form, and the description's mention of `top` and its default 50 merely restates the schema. The `format` parameter (html vs markdown) is never referenced in the description, so no meaning is added beyond the schema.

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 opens with a specific verb+resource pair, 'List comments on a work item,' which scopes the operation to work items and implicitly separates it from the pull-request comment sibling. It is clear about what is returned, though it never names an alternative tool for contrast.

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, no prerequisites, and no mention of when a different tool (e.g. the PR thread comment lister or the comment-write siblings) would be the right call. Usage is only inferable from the verb 'List'.

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