Skip to main content
Glama
Sign In
ado-mcp

ado-mcp

by og-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

ado_create_branch

Create a new branch from an existing source branch in an Azure DevOps repository.

Instructions

Create a new branch from the tip of an existing source branch.

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": {
      "repoId": "<repoId>",
      "newBranch": "<newBranch>",
      "sourceBranch": "<sourceBranch>"
    },
    "name": "ado_create_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoIdYesRepository name or ID
projectNoProject name or ID (defaults to ADO_DEFAULT_PROJECT)
newBranchYesNew branch name (without refs/heads/)
sourceBranchYesExisting branch to branch from, e.g. "main"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description must convey behavioral traits. It states the tool creates a branch from a source tip (a mutation), but does not disclose side effects, authorization requirements, or rate limits. Adequate but minimal.

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?

Single sentence, 13 words, front-loaded with action and resource. No wasted words; every part earns its place.

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?

Description covers the core operation but omits details like conflict behavior or whether the branch is remote. For a simple branch creation tool, this is adequate but not 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?

Schema covers 100% of parameters with descriptions. The tool description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

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?

Description clearly states the action (create), resource (branch), and specific behavior (from the tip of an existing source branch), effectively distinguishing it from sibling tools like list_branches and get_branch.

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?

No explicit guidance on when or when not to use this tool, nor alternatives. Usage is implied by the tool's purpose, but the description lacks any contextual cues for choosing this over other branch-related tools.

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