HAOps MCP Server

haops_review_merge_request

Submit a review verdict to approve, request changes, or comment on a merge request. Automatically transitions MR status when approval thresholds are met.

Instructions

Submit a review on a merge request. Verdicts: approved, changes_requested, commented. When enough approvals are met (per branch protection rules), MR status auto-transitions to approved.

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": {
      "projectSlug": "<projectSlug>",
      "mergeRequestId": "<mergeRequestId>",
      "verdict": "<verdict>"
    },
    "name": "haops_review_merge_request"
  }
}

Input Schema

Name	Required	Description
`body`	No	Review comment (optional)
`verbose`	No	If true, return the full API response instead of the compact summary (default: false)
`verdict`	Yes	Review verdict
`projectSlug`	Yes	The project slug (URL identifier)
`mergeRequestId`	Yes	MR UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Jul 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the verdicts and auto-transition, but lacks details on idempotency, permissions, whether reviews can be overwritten, or the return format. This is adequate but not comprehensive.

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 two sentences, front-loaded with the main action, and every sentence adds value. No unnecessary words or repetition.

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

Completeness4/5

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

Given the five parameters, no output schema, and no annotations, the description covers the core purpose, verdict options, and a key behavioral aspect (auto-transition). It lacks information on permissions or error states, but for a review action, it provides sufficient context for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter is documented. The description adds meaning by explaining the verdict values and their effect (auto-transition), which provides context beyond the enum listing. However, it does not add specific details to other parameters like body or verbose.

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

Purpose5/5

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

The description clearly states 'Submit a review on a merge request' with a specific verb and resource. It lists the three verdicts and mentions auto-transition behavior, distinguishing it from sibling tools like merge, close, reopen, and get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when the tool is used (submitting a review) and notes that when enough approvals are met, the MR status auto-transitions to approved. It does not explicitly state when not to use it or compare to alternatives, but the context is clear for a review action.

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

Deploy Server