Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

compare

Compare code changes between commits, branches, or tags in Alibaba Cloud DevOps repositories to review differences and track modifications.

Instructions

[Code Management] Query code to compare content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID, can be found in the basic information page of the organization admin console
repositoryIdYesRepository 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)
fromYesCan be CommitSHA, branch name or tag name
toYesCan be CommitSHA, branch name or tag name
sourceTypeNoOptions: branch, tag; if it's a commit comparison, you can omit this; if it's a branch comparison, you need to provide: branch, or you can omit it but ensure there are no branch or tag name conflicts; if it's a tag comparison, you need to provide: tag; if there are branches and tags with the same name, you need to strictly provide branch or tag
targetTypeNoOptions: branch, tag; if it's a commit comparison, you can omit this; if it's a branch comparison, you need to provide: branch, or you can omit it but ensure there are no branch or tag name conflicts; if it's a tag comparison, you need to provide: tag; if there are branches and tags with the same name, you need to strictly provide branch or tag
straightNoWhether to use Merge-Base: straight=false means using Merge-Base; straight=true means not using Merge-Base; default is false, meaning using Merge-Base

Implementation Reference

  • Handler for the 'compare' tool: parses input using GetCompareSchema and invokes getCompareFunc from operations/codeup/compare.js, returning the result as JSON.
    case "compare": {
      const args = types.GetCompareSchema.parse(request.params.arguments);
      const compareResult = await compare.getCompareFunc(
        args.organizationId,
        args.repositoryId,
        args.from,
        args.to,
        args.sourceType ?? undefined,
        args.targetType ?? undefined,
        args.straight ?? undefined
      );
    
      return {
        content: [{ type: "text", text: JSON.stringify(compareResult, null, 2) }],
      };
    }
  • Input schema (GetCompareSchema) for the 'compare' tool, defining parameters like organizationId, repositoryId, from, to, etc.
    export const GetCompareSchema = z.object({
      organizationId: z.string().describe("Organization ID, can be found in the basic information page of the organization admin console"),
      repositoryId: z.string().describe("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)"),
      from: z.string().describe("Can be CommitSHA, branch name or tag name"),
      to: z.string().describe("Can be CommitSHA, branch name or tag name"),
      sourceType: z.string().nullable().optional().describe("Options: branch, tag; if it's a commit comparison, you can omit this; if it's a branch comparison, you need to provide: branch, or you can omit it but ensure there are no branch or tag name conflicts; if it's a tag comparison, you need to provide: tag; if there are branches and tags with the same name, you need to strictly provide branch or tag"),
      targetType: z.string().nullable().optional().describe("Options: branch, tag; if it's a commit comparison, you can omit this; if it's a branch comparison, you need to provide: branch, or you can omit it but ensure there are no branch or tag name conflicts; if it's a tag comparison, you need to provide: tag; if there are branches and tags with the same name, you need to strictly provide branch or tag"),
      straight: z.string().default("false").nullable().optional().describe("Whether to use Merge-Base: straight=false means using Merge-Base; straight=true means not using Merge-Base; default is false, meaning using Merge-Base"),
    });
  • Registration of the 'compare' tool in getCodeManagementTools array, specifying name, description, and inputSchema.
    {
      name: "compare",
      description: "[Code Management] Query code to compare content",
      inputSchema: zodToJsonSchema(types.GetCompareSchema),
    },
  • Core helper function getCompareFunc that performs the API call to Codeup compare endpoint and parses response with CompareSchema.
    export async function getCompareFunc(
      organizationId: string,
      repositoryId: string,
      from: string,
      to: string,
      sourceType?: string, // Possible values: branch, tag
      targetType?: string, // Possible values: branch, tag
      straight?: string
    ): Promise<z.infer<typeof CompareSchema>> {
      const encodedRepoId = handleRepositoryIdEncoding(repositoryId);
    
      const baseUrl = `/oapi/v1/codeup/organizations/${organizationId}/repositories/${encodedRepoId}/compares`;
    
      const queryParams: Record<string, string | undefined> = {
        from,
        to
      };
      
      if (sourceType !== undefined) {
        queryParams.sourceType = sourceType;
      }
      
      if (targetType !== undefined) {
        queryParams.targetType = targetType;
      }
      
      if (straight !== undefined) {
        queryParams.straight = straight;
      }
    
      const url = buildUrl(baseUrl, queryParams);
    
      const response = await yunxiaoRequest(url, {
        method: "GET",
      });
    
      return CompareSchema.parse(response);
    } 
  • Output schema (CompareSchema) used to parse the response from the compare API in getCompareFunc.
    export const CompareSchema = z.object({
      base_commit_sha: z.string().optional(),
      commits: z.array(z.unknown()).optional(),
      commits_count: z.number().optional(),
      diffs: z.array(z.unknown()).optional(),
      files_count: z.number().optional(),
      from: z.string().optional(),
      to: z.string().optional(),
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'Query' which suggests a read-only operation, but does not disclose behavioral traits like whether it's safe, if it requires authentication, rate limits, or what the output looks like (e.g., diff format). The description is minimal and lacks critical context for a tool with 7 parameters.

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 concise with a single sentence, front-loaded with the purpose. However, it could be more structured by including key usage notes. There is no wasted text, but it might be overly brief given the tool's complexity.

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

Completeness2/5

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

Given the complexity (7 parameters, no annotations, no output schema), the description is incomplete. It does not explain what the comparison outputs (e.g., diff, changes), error conditions, or how it integrates with sibling tools. For a comparison tool in code management, more context is needed to guide effective use.

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 all parameters thoroughly. The description adds no additional meaning beyond what the schema provides, such as explaining the relationship between 'from' and 'to' or the purpose of 'straight'. Baseline is 3 since the schema does the heavy lifting.

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

Purpose3/5

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

The description states the tool 'Query code to compare content' which indicates a comparison operation on code content, but it's vague about what specifically is being compared (e.g., commits, branches, files). It distinguishes from siblings like 'get_commit' or 'list_commits' by focusing on comparison rather than retrieval, but lacks specificity about the comparison scope or output format.

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 explicit guidance on when to use this tool versus alternatives is provided. The description does not mention prerequisites, such as needing repository access, or differentiate from similar tools like 'get_commit' for single commit details. Usage is implied through parameter context but not stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aliyun/alibabacloud-devops-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server