Apply a specific suggestion to a merge request by providing its ID, confirming the action, and receiving a confirmation with details.
Apply a single suggestion to the merge request.
Args: suggestion_id: Suggestion ID to apply
Returns: Confirmation message with apply details
| Name | Required | Description | Default |
|---|---|---|---|
| suggestion_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states 'apply' which implies a mutation, but does not disclose side effects, permissions required, or whether the operation is reversible.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise with no unnecessary words. Two short sentences convey the purpose and parameter clearly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-parameter operation, the description is adequate. It could mention what the result looks like (e.g., returns confirmation), but not strictly necessary given the simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (only one parameter), and the description mirrors the schema ('Suggestion ID to apply'). It adds no additional semantic detail beyond what is already in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specifies a clear verb ('apply') and resource ('suggestion to the merge request'), and distinguishes from the sibling tool 'apply_suggestions' by emphasizing 'single'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use it (for a single suggestion) but does not explicitly state when not to use it or mention the plural alternative. Lacks explicit guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.