gitlab-mcp

Overview Schema Source Related Servers Discussions Admin

compare_refs

Compare differences between two Git references (branches, tags, or commits) in a GitLab project. Specify project ID and source/target refs to view the diff.

Instructions

두 ref 간 diff 비교 (브랜치/태그/커밋)

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_id": "<project_id>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "compare_refs"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	대상 ref (브랜치/태그/SHA)
`from`	Yes	기준 ref (브랜치/태그/SHA)
`instance`	No	대상 GitLab 인스턴스명 (생략 시 default)
`straight`	No	직선 비교 여부
`file_path`	No	특정 파일만 조회
`max_lines`	No	파일당 최대 라인 (기본 1000)
`project_id`	Yes	프로젝트 ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Jul 30, 2026

TDQS

C2.7/5.0

Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'diff between two refs' without explaining what is returned, permission requirements, error cases, or details about parameters like 'straight'. This is severely lacking.

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

Conciseness3/5

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

The description is very short (7 words in Korean), making it concise but not well-structured. It lacks any logical breakdown or hierarchy, though it does not waste words. It is average because it is too minimal.

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

Completeness1/5

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

Given the tool has 7 parameters, no output schema, and no annotations, the description is grossly incomplete. It does not cover return format, pagination, limitations, or integration context, leaving significant gaps for agent understanding.

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 each parameter has a description in the schema. The tool description does not add meaningful additional information beyond what the schema already provides, keeping the score at the baseline of 3.

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 tool compares differences between two refs (branches, tags, commits). It uses a specific verb 'compare' and resource 'refs', and distinguishes from sibling tools like get_mr_diff (for merge requests) and get_commit_diff (for a single commit).

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 like get_mr_diff or get_commit_diff. The description does not mention scenarios, prerequisites, or exclusions, forcing the agent to infer usage from context.

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