Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_branch

Retrieve branch details from a Codeup repository, including name and existence, using organization, repository, and branch identifiers.

Instructions

[Code Management] Get information about a branch in a Codeup repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branchNameYesBranch name (if it contains special characters, use URL encoding), example: master or feature%2Fdev
repositoryIdYesRepository ID, or org/repo path with slashes URL-encoded as %2F. e.g. 2835387 or myorg%2Fmyrepo
organizationIdYesOrganization ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.60
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / organizationId / description
      Previous value: -"Organization ID, can be found in the basic information page of the organization admin console"New value: +"Organization ID"
    • changedInput schema / properties / repositoryId / description
      Previous value: -"Repository ID or a combination of organization ID and repository name, for example: 2835387 or organizationId%2Frepo-name (Note: slashes need to be URL encoded as %2F)"New value: +"Repository ID, or org/repo path with slashes URL-encoded as %2F. e.g. 2835387 or myorg%2Fmyrepo"
    • changedInput schema / properties / repositoryId / type
      Previous value: -"string"New value: +[
+  "string",
+  "number"
+]
  2. 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, the description must carry the full burden of behavioral disclosure. It only says 'get information about a branch', with no mention of return shape, error conditions, read-only guarantees, or special behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one concise, easily parsed sentence. The '[Code Management]' category prefix is somewhat redundant but does not significantly reduce quality.

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 simple get operation with no output schema and no annotations, an agent would likely want more context about the response structure or branch identity details. The description is adequate but leaves the actual information returned unstated.

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 already documents all three parameters with clear descriptions (100% coverage), so the description adds no additional parameter-level meaning. The baseline of 3 is appropriate since the schema handles the heavy lifting.

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 specifies a clear action ('get information') and a target ('a branch in a Codeup repository'), distinguishing it from sibling tools like list_branches or create_branch. It is not a tautology, though it could be more specific about what branch details are returned.

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?

No guidance is provided about when to use this tool versus alternatives such as list_branches or get_file_blobs. There are no mentions of prerequisites, exclusions, or contrasting scenarios.

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