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

repo_reply_to_comment

Respond to pull request comments in Azure DevOps repositories by specifying repository, PR, thread IDs, and content. Simplify collaboration with direct replies using PAT authentication.

Instructions

Replies to a specific comment on a pull request.

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": {
      "repositoryId": "<repositoryId>",
      "pullRequestId": "<pullRequestId>",
      "threadId": "<threadId>",
      "content": "<content>"
    },
    "name": "repo_reply_to_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesThe content of the comment to be added.
fullResponseNoReturn full comment JSON response instead of a simple confirmation message.
projectNoProject ID or project name (optional)
pullRequestIdYesThe ID of the pull request where the comment thread exists.
repositoryIdYesThe ID of the repository where the pull request is located.
threadIdYesThe ID of the thread to which the comment will be added.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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. While 'Replies to' implies a write operation, the description doesn't mention authentication requirements, permission levels needed, rate limits, whether replies are editable/deletable, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is insufficient behavioral context.

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 the tool's complexity and gets straight to the point without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is minimally adequate but has significant gaps. It states what the tool does but lacks behavioral context, usage guidance, and output information. The 100% schema coverage helps, but the description should do more given this is a write operation with multiple parameters.

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?

The schema description coverage is 100%, so the schema already documents all 6 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema (like explaining the relationship between repositoryId, pullRequestId, and threadId). With high schema coverage, the baseline score of 3 is appropriate.

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 ('Replies to') and target ('a specific comment on a pull request'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'wit_add_work_item_comment' or 'repo_create_pull_request_thread' that also handle comments in different contexts, so it doesn't achieve full sibling differentiation.

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. There are multiple comment-related tools in the sibling list (e.g., 'wit_add_work_item_comment', 'repo_create_pull_request_thread'), but the description doesn't indicate this is specifically for replying to existing pull request comment threads versus creating new threads or commenting on work items.

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