Skip to main content
Glama
Sign In
Azure DevOps MCP Server with PAT Authentication

Azure DevOps MCP Server with PAT Authentication

by ennuiii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

wit_add_work_item_comment

Add comments to Azure DevOps work items using ID, specifying text and format (markdown or HTML) for efficient task collaboration and updates.

Instructions

Add comment to a work item by ID.

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": {
      "project": "<project>",
      "workItemId": "<workItemId>",
      "comment": "<comment>"
    },
    "name": "wit_add_work_item_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesThe text of the comment to add to the work item.
formatNohtml
projectYesThe name or ID of the Azure DevOps project.
workItemIdYesThe ID of the work item to add a comment to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an 'Add' operation (implying mutation/write), but doesn't mention authentication requirements, permission levels, whether comments are editable/deletable, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is insufficient.

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 a single, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential action and target.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after adding a comment (success response, error conditions), doesn't mention the Azure DevOps context implied by parameters, and provides no behavioral context. The description alone is inadequate for safe tool invocation.

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 75% (3 of 4 parameters have descriptions), so the baseline is 3. The description mentions 'by ID' which hints at the workItemId parameter, but doesn't add meaningful context beyond what the schema already provides about project, workItemId, comment, or format parameters.

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 clearly states the action ('Add comment') and target resource ('to a work item by ID'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'wit_list_work_item_comments' or 'repo_reply_to_comment', but the verb+resource combination is specific enough for basic understanding.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'wit_list_work_item_comments' (for reading comments) or 'repo_reply_to_comment' (for repository comments), nor does it specify prerequisites like needing a work item ID or project context.

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

Deploy Server

Other Tools

Related Tools