Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidcheck

getChangesChangeIdCheck

Run consistency checks on a Gerrit change to surface its problems as a list of problem entries, so you can validate the change before review or submission.

Instructions

Performs consistency checks on the change, and returns a ChangeInfo entity with the problems field set to a list of ProblemInfo entities.

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>"
    },
    "name": "getChangesChangeIdCheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of explaining behaviour. It implies a read-only evaluation, but it never says whether the tool mutates state, what permissions are needed, whether the checks are cached, or how expensive the call is. The only behavioural detail it gives, the return payload shape, overlaps with what the output schema already covers.

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?

The description is a single well-formed sentence with the action front-loaded and no filler. It is appropriately short, though what brevity it gains comes partly at the cost of the missing usage and parameter detail noted elsewhere.

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

Completeness3/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 description needn't explain return values in depth, although it restates the problems list anyway. For a one-parameter read tool this is close to adequate, but the absence of any identifier format hint or routing guidance against the many sibling check tools leaves real gaps.

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?

The schema has one required parameter, change-id, with 0% description coverage, so the description should explain its format, for example a project/repo~changeId style identifier. It says nothing about the parameter, which leaves the agent to guess the identifier format from the parameter name alone.

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 names a specific verb and resource: it performs consistency checks on a change and returns a ChangeInfo with the problems field populated. That clearly describes what the tool does. It doesn't, however, say how this differs from neighbouring check-related siblings such as checks_getChangesChangeIdRevisionsRevisionIdChecks, so it stops short of a 5.

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 guidance on when to use this tool, when not to use it, or which sibling to use instead. The description never mentions prerequisites, permissions, or the relationship to the revision-level checks tools, so the agent has to infer usage from the name alone.

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