Skip to main content
Glama

create_merge_request_discussion_note

Add a note to an existing merge request discussion thread to provide feedback, ask questions, or continue collaboration on code changes.

Instructions

Add a new discussion note to an existing merge request thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject ID or complete URL-encoded path to project
merge_request_iidNoThe IID of a merge request
discussion_idNoThe ID of a thread
bodyYesThe content of the note or reply
created_atNoDate the note was created at (ISO 8601 format)

Implementation Reference

  • Input schema definition for the 'create_merge_request_discussion_note' tool, defining parameters like project_id, merge_request_iid, discussion_id, body, and optional created_at.
      merge_request_iid: z.coerce.string().describe("The IID of a merge request"),
      discussion_id: z.coerce.string().describe("The ID of a thread"),
      body: z.string().describe("The content of the note or reply"),
      created_at: z.string().optional().describe("Date the note was created at (ISO 8601 format)"),
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as required permissions (e.g., project access), whether this is a mutation (implied by 'Add'), rate limits, or what happens on success/failure. The description is minimal and lacks critical operational context for a write operation.

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, efficient sentence that front-loads the core purpose without any wasted words. It's appropriately sized for the tool's complexity, making it easy to parse quickly.

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 tool's complexity (a write operation with 5 parameters) and lack of annotations or output schema, the description is incomplete. It doesn't address key aspects like return values, error conditions, or behavioral nuances, leaving significant gaps for an AI agent to understand how to invoke it correctly.

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?

The description adds no parameter-specific information beyond what's already in the schema, which has 100% coverage with clear descriptions for all 5 parameters. The baseline is 3 because the schema does the heavy lifting, but the description doesn't compensate with additional context like parameter interactions or examples.

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 clearly states the action ('Add a new discussion note') and target resource ('to an existing merge request thread'), which is specific and unambiguous. It distinguishes from siblings like 'create_merge_request_note' (which creates a standalone note) by specifying it's for a thread, though it doesn't explicitly name alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives like 'create_merge_request_note' or 'update_merge_request_discussion_note'. It mentions 'existing merge request thread' but doesn't clarify prerequisites (e.g., thread must exist) or exclusions, leaving usage context implied rather than explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zereight/gitlab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server