Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidreview

getChangesChangeIdRevisionsRevisionIdReview

Retrieve a revision's change details with review-relevant fields, including labels and messages, to support Gerrit review decisions.

Instructions

Retrieves a change with the review-relevant fields (labels, messages) for a revision.

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": "getChangesChangeIdRevisionsRevisionIdReview"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
revision-idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full disclosure burden. It does add value by indicating the response contains review-relevant fields such as labels and messages, but it says nothing about permissions required, whether this is a read-only lookup, error behavior for unknown change/revision ids, or pagination.

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 efficient, though its brevity is close to under-specification rather than tight communication.

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?

With no annotations, no output schema, 0% parameter coverage, and a dense set of near-identically-named siblings, the definition needs more than one sentence to be callable with confidence. It does not explain what the review-relevant field subset is relative to the full revision resource, nor how it differs from adjacent endpoints.

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%, so both required parameters (change-id, revision-id) rely entirely on the description for meaning. The description never mentions either parameter or their formats, so it fails to compensate for the coverage gap; only the self-explanatory names help.

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 ("Retrieves") and resource (a change's review-relevant fields for a revision), and it specifies the returned content (labels, messages). It does not explicitly distinguish itself from the base getChangesChangeIdRevisionsRevisionId endpoint or from the reviewers siblings, leaving the agent to infer the difference from the name alone.

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 statement of when to use this tool versus the plain revision endpoint or the reviewer/reviewers endpoints, and no prerequisites or exclusions are given. The agent must infer usage entirely from the tool name.

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