Git MCP Server

Overview Schema Source Related Servers Discussions Admin

get_merge_request_details

Retrieve detailed information about a specific merge request, including its status, changes, and discussions, to review and analyze code changes.

Instructions

Get detailed information about a specific merge request

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": {
      "platform": "<platform>",
      "project_id": "<project_id>",
      "mr_id": "<mr_id>"
    },
    "name": "get_merge_request_details"
  }
}

Input Schema

Name	Required	Description	Default
`mr_id`	Yes
`platform`	Yes
`project_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.5Jul 30, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only says 'get', implying a read-only operation, but does not explicitly state it is safe (no side effects), mention any required permissions, or describe the output format. The presence of an output schema alleviates some burden, but the description lacks detail on behavioral traits.

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 a single sentence that is front-loaded with the core action and resource. It is concise with no fluff, but it may be too succinct given the lack of parameter explanations.

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 simplicity of the tool (3 required string parameters) and the absence of annotations and parameter descriptions, the description is incomplete. It does not define what 'detailed information' includes, nor does it explain the parameters or provide usage context. The output schema helps but is not enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning no parameter descriptions exist in the schema. The tool description does not compensate by explaining what 'mr_id', 'platform', and 'project_id' represent. Without this, an agent cannot determine the correct values for these parameters.

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 action ('get') and the resource ('detailed information about a specific merge request'). It distinguishes from sibling tools like 'list_merge_requests' (which lists) and 'get_merge_request_diff' (which gets a diff).

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 when full details of a merge request are needed, but it does not provide explicit guidance on when to use this tool versus alternatives like 'get_merge_request_diff' or 'get_merge_request_commits', nor does it mention any prerequisites.

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