Skip to main content
Glama
Sign In
mcp-gitlab-crunchtools

mcp-gitlab-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Merge Request Tool

get_merge_request_tool
Read-only

Fetch a single merge request by project ID and internal IID to inspect its details, changes, and status.

Instructions

Get a single merge request by its IID.

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>",
      "merge_request_iid": "<merge_request_iid>"
    },
    "name": "get_merge_request_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID or path
merge_request_iidYesMerge request internal ID (the number shown in the UI, e.g., !42)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / merge_request_iid / minimum
      Added value: +1
  2. First observedv0.4.1

TDQS

B3.2/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds no behavioral context beyond that, such as required access scope, response behavior, or relationship to similar retrieval tools.

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 efficient sentence with the key operation and lookup key front-loaded. It is not verbose, though it is so terse that it omits useful routing context.

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

Completeness3/5

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

The tool is simple and the input schema, output schema, and readOnly annotation cover most technical details. Still, given the dense set of sibling tools involving merge requests, the description would benefit from clarifying when to use this tool instead of list_merge_requests_tool or get_mr_changes_tool.

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 explains both project_id and merge_request_iid in detail. The description's 'by its IID' restates the schema's merge_request_iid semantics without adding new format or handling details, making the baseline 3 appropriate.

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

Purpose4/5

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

The description uses a clear verb-resource pair ('Get a single merge request') and adds the lookup key ('by its IID'). It is distinguishable from list_merge_requests_tool, but it does not explicitly distinguish itself from related retrieval tools such as get_mr_changes_tool.

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 phrase 'single merge request by its IID' implies usage when the caller knows a specific MR IID, which indirectly differentiates it from list_merge_requests_tool. However, no explicit when-to-use, when-not-to-use, or alternative-selection guidance is provided.

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