gitlab-mcp

by wisesky0

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

get_merge_request

Retrieve merge request details with diff references using project ID and MR IID.

Instructions

MR 상세 조회 (diff_refs 포함)

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_merge_request"
  }
}

Input Schema

Name	Required	Description
`mr_iid`	Yes	MR iid
`instance`	No	대상 GitLab 인스턴스명 (생략 시 default)
`project_id`	Yes	프로젝트 ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Jul 30, 2026

TDQS

B3.4/5.0

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 inclusion of diff_refs but does not disclose read-only nature, authentication requirements, or any side effects. For a read operation, minimal behavioral context is given.

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?

A single, concise sentence that front-loads the core purpose. Every word is informative, with no redundancy.

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?

With no output schema and no annotations, the description is minimal. It does not explain the return format or the extent of 'detailed MR' beyond diff_refs. The agent may need additional context to fully understand the tool's output.

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. The description adds no additional parameter meaning beyond the schema's 'MR iid' and 'project ID' descriptions. 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_refs 포함)' meaning detailed MR view including diff_refs. It succinctly communicates the tool's function and distinguishes it from siblings like list_merge_requests (listing) and get_mr_diff (diff only).

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?

The description implies usage for obtaining detailed MR info with diff_refs, but does not explicitly state when to use it versus alternatives like list_merge_requests or get_mr_diff. No exclusions or prerequisites are mentioned.

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