arcade-azure-devops-mcp

AzureDevops_ListBranches

AzureDevops_ListBranches

List branches in an Azure DevOps repository, with optional filters to search by name substring or cap the number of results, helping you quickly identify relevant branches.

Instructions

List branches in a repository.

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>",
      "repository_id": "<repository_id>"
    },
    "name": "AzureDevops_ListBranches"
  }
}

Input Schema

Name	Required	Description
`top`	No	Maximum number of branches to return
`project`	Yes	Project name or ID
`repository_id`	Yes	Repository name or ID
`filter_contains`	No	Filter branches containing this string

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention any potential side effects, required permissions, rate limits, or output structure. While 'List' implies a read-only operation, the description offers no additional context about behavior beyond what is inherent in the verb.

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 redundant information. It conveys the core purpose efficiently and is appropriately sized for the tool's simplicity.

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?

The tool has a modest schema with 4 parameters and no output schema. The description does not explain return values, pagination, or filtering behavior, but the schema covers the parameters. Given the simplicity of the tool, a 'List branches' description is acceptable, but it lacks some contextual detail that would make it fully complete.

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 input schema provides descriptions for all 4 parameters, achieving 100% coverage. The description adds no extra meaning beyond the schema, but per the calibration baseline, a score of 3 is appropriate when the schema fully documents parameters. The optional 'top' and 'filter_contains' parameters are described in the schema, not the description.

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 verb 'List' with a specific resource ('branches') and scoping ('in a repository'). This distinguishes it from sibling tools like AzureDevops_ListRepositories and AzureDevops_ListBuilds, making the tool's purpose unambiguous.

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 explicit guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusion conditions. The description simply restates the function without providing context about when it is the appropriate choice, such as when a user needs to inspect branch names in a specific repo.

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