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

mcp-gitlab-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Merge Requests Tool

list_merge_requests_tool
Read-only

Query and retrieve merge requests for any GitLab project. Use advanced filters to search by label, milestone, state, or project ID.

Instructions

List merge requests for a GitLab project.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sortNoSort direction (asc, desc)desc
stateNoFilter by state (opened, closed, merged, all)opened
labelsNoComma-separated label names
searchNoSearch in title and description
order_byNoOrder by field (created_at, updated_at)created_at
per_pageNoResults per page, max 100 (default: 20)
milestoneNoMilestone title
project_idYesProject ID or path

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered, but the description adds nothing beyond the title: it never mentions that only 'opened' MRs are returned by default (state defaults to 'opened'), nor anything about pagination caps or result volume. For a paginated list tool, the default filter is the single most important behavioral fact and it is omitted.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity is achieved by omission rather than by tight editing.

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?

With an output schema present, return-value explanation is not required, and the input schema fully documents all parameters. What is missing is behavioral context an agent needs to call it correctly — notably the opened-by-default state and the 100-item per_page ceiling's effect on paging.

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%, with every one of the 9 parameters (page, per_page, state, labels, search, order_by, sort, milestone, project_id) documented in the schema itself. The description adds no filtering semantics beyond that, so baseline 3 applies.

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?

States a specific verb (List) and resource (merge requests) plus the scope (for a GitLab project), so an agent knows exactly what it returns at a high level. It does not differentiate from siblings such as get_merge_request_tool (single MR) or list_issues_tool, but the verb/resource pairing alone is unambiguous.

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?

There is no guidance on when to use this tool versus get_merge_request_tool, list_mr_notes_tool, or search_project_tool, and no prerequisites or exclusions are stated. Everything is left to inference from the tool name.

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