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

mcp-gitlab-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Mr Discussion Tool

create_mr_discussion_tool

Creates a new discussion on a GitLab merge request using the project ID or path, merge request IID, and Markdown body.

Instructions

Create a new discussion on a 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": {
      "project_id": "<project_id>",
      "merge_request_iid": "<merge_request_iid>",
      "body": "<body>"
    },
    "name": "create_mr_discussion_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesDiscussion body (Markdown)
project_idYesProject ID or path
merge_request_iidYesMerge request internal ID

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

C2.9/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 the full behavioral burden. It says only that a discussion is created, without disclosing permissions needed, side effects, notification behavior, or whether this starts a threaded discussion versus a flat note.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately sized for the limited information it chooses to convey.

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?

For a mutation tool with no annotations and a sibling that also creates merge-request content, the description is incomplete. It does not clarify discussion-versus-note semantics, prerequisites, or when the agent should choose this tool over create_mr_note_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%, and all three required parameters are documented in the schema. The description adds no additional meaning about parameter formats or constraints, so the baseline of 3 is 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 states a clear verb and resource: create a new discussion on a merge request. It is specific enough to understand the basic action, but it does not differentiate this tool from the sibling create_mr_note_tool, which also creates content on a merge request.

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 instead of create_mr_note_tool or how it relates to list_mr_discussions_tool. The agent must infer that this creates a discussion thread rather than adding a note to an existing discussion.

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