Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidmergeable

getChangesChangeIdRevisionsRevisionIdMergeable

Checks whether a Gerrit change revision can merge into its destination branch and optionally verifies mergeability against other branches.

Instructions

Returns whether a revision can be merged into the destination branch as a MergeableInfo entity.

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": {
      "change-id": "<change-id>",
      "revision-id": "<revision-id>"
    },
    "name": "getChangesChangeIdRevisionsRevisionIdMergeable"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
revision-idYes
other-branchesNo

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 supplied, so the description carries the full disclosure burden, yet it says nothing about whether this is a pure read, whether it triggers an actual merge trial on the server, what happens when the branch is out of date, or any auth/rate-limit constraints. The only behavioral hint is the word 'Returns', which weakly implies a non-mutating operation.

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; the outcome and return entity come first. It is efficient, though the brevity is partly a symptom of under-specification rather than disciplined editing.

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 return values need not be described, but for a three-parameter, zero-annotation tool the description leaves too much open: no parameter meaning, no usage conditions, and no behavioral context. An agent would have to guess at 'other-branches' and at what the call costs.

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% for three parameters, and the description explains none of them. 'Revision' and 'destination branch' loosely gesture at change-id/revision-id, but the optional 'other-branches' boolean — which plausibly changes the semantics of the result — is left completely undefined.

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?

States a specific verb and outcome: 'Returns whether a revision can be merged into the destination branch', naming the resource (revision) and the return entity (MergeableInfo). This is clearly distinguishable from siblings like getMergelist or getSubmitType, though it never explicitly contrasts itself with them.

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, no statement of prerequisites (e.g. the change/revision must exist, permissions needed), and no mention of the related merge-check siblings. The intended use is only inferable from the verb 'mergeable'.

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