Skip to main content
Glama
Sign In
gitlab-mcp

gitlab-mcp

by wisesky0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_mr_diff

Retrieve merge request diffs from GitLab with file-level splitting. Filter by file path and paginate through results.

Instructions

MR diff 조회 (/diffs, 파일 단위 분할)

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>",
      "mr_iid": "<mr_iid>"
    },
    "name": "get_mr_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo페이지 번호 (1부터)
mr_iidYesMR iid
instanceNo대상 GitLab 인스턴스명 (생략 시 default)
per_pageNo페이지당 개수 (기본 20)
file_pathNo특정 파일만 조회 (선택)
max_linesNo파일당 최대 라인 (기본 1000)
project_idYes프로젝트 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic purpose and endpoint but does not reveal behavior such as pagination limits, error handling, authentication needs, or implications of the 'file unit split' (e.g., how diffs are aggregated).

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 very short and to the point, containing only essential information (endpoint and file-splitting aspect). No redundant words, though it could benefit from a brief English equivalent for wider clarity.

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 tool has 7 parameters, no output schema, and no annotations, the single-sentence description is insufficient. It does not explain the return format, pagination behavior, or how file-splitting works, leaving gaps for an AI agent to infer.

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 coverage is 100% with all parameters described in the input schema. The description adds no extra parameter-level meaning beyond what the schema already provides, so a baseline score 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?

The description clearly states 'MR diff 조회' (MR diff query) and the endpoint '/diffs' with '파일 단위 분할' (file unit split), which precisely defines the tool's function. It is distinct from siblings like `get_mr_discussions` or `get_mr_participants`.

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 on when to use this tool versus alternatives. For example, it doesn't mention that `get_mr_discussions` should be used for comments instead of diffs. The description also lacks prerequisites or context for invocation.

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