Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidbranchesbranchidmergeable

getProjectsProjectIdBranchesBranchIdMergeable

Checks whether a source is mergeable with the target branch in a Gerrit project, returning mergeability status for review and integration decisions.

Instructions

Gets whether the source is mergeable with the target branch.

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>",
      "branch-id": "<branch-id>",
      "source": "<source>"
    },
    "name": "getProjectsProjectIdBranchesBranchIdMergeable"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
strategyNo
branch-idYes
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 burden. It does not say whether this performs an actual trial merge, whether it is expensive or rate-limited, what permissions are required, or whether results can be stale. For a check that may trigger server-side merge computation, that is a meaningful gap.

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 no filler or redundancy. It is terse rather than bloated, so the only knock is that the brevity is achieved by omitting information rather than by efficient phrasing.

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?

An output schema exists, so the return shape need not be explained. But with zero annotation coverage, no parameter documentation, and an unmentioned 'strategy' input, the definition is not complete enough for an agent to call this confidently without trial and error.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters. The description only implies that 'source' is the branch being tested against the branch identified by branch-id; it says nothing about the 'strategy' parameter (merge vs. squash vs. rebase?) or the identifier formats for project-id and branch-id. This leaves the agent guessing on a required parameter set of three.

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 specific verb and resource: it reports whether the given source is mergeable with the target branch. That is a clear operation an agent can distinguish from generic branch reads. However, it does not clarify how this differs from the sibling getChangesChangeIdRevisionsRevisionIdMergeable, nor what 'mergeable' means concretely (conflict check vs. policy check).

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 when-to-use guidance: nothing about prerequisites, when a mergeability check is appropriate versus reading branch details or validation options, or what to do when the result is false. The only implied usage comes from the verb itself.

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