Skip to main content
Glama
dockndevai

mcp-azure-devops

by dockndevai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List pull requests

list_pull_requests
Read-onlyIdempotent

List pull requests from an Azure DevOps repo, with optional status filter to view active, completed, or all PRs.

Instructions

List pull requests in a repository, optionally filtered by status (active by default).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoYesRepository id or name (from list_repositories)
statusNoFilter by PR status; defaults to 'active'
projectYesProject name or id (must be within AZDO_PROJECT_ALLOWLIST when that is set)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.3
    • addedInput schema / properties / project / description
      Added value: +"Project name or id (must be within AZDO_PROJECT_ALLOWLIST when that is set)"
    • addedInput schema / properties / repo / description
      Added value: +"Repository id or name (from list_repositories)"
    • changedInput schema / properties / status / description
      Previous value: -"Default active"New value: +"Filter by PR status; defaults to 'active'"
  2. Changed1 schema field changedv0.2.2
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to repeat those. It adds value by stating the default status filter ('active by default'), which is behavioral information not in the schema or annotations. This supplements the structured metadata effectively.

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, front-loaded sentence with no fluff. It communicates the primary action, optional filter, and default behavior efficiently. Every word earns its place, making it highly concise and well-structured.

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

Completeness4/5

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

For a simple read-only list operation, the description covers the key behavior (listing by repository with an optional status filter) and functional details like the default. It omits pagination or response format, but these are not critical given the tool's simplicity and the safety annotations. Overall, it is complete enough for an agent to call correctly.

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 the schema already documents each parameter. The description reinforces the `status` parameter's default but does not add new meaning beyond what the schema provides for repo and project. The baseline of 3 is appropriate when the schema carries the full parameter burden.

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

Purpose5/5

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

The description clearly states the action ('List') and the resource ('pull requests in a repository'), and specifies an optional filter on status with a default. This distinguishes it from sibling get_pull_request (which fetches a single PR) and other list tools by naming the exact scope.

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 when to use it (to list PRs) but does not explicitly contrast with siblings like get_pull_request or mention when NOT to use it. There is no guidance on selecting between this and get_pull_request for a single item, though the filter hint ('active by default') provides some 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