Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidpatch

getChangesChangeIdRevisionsRevisionIdPatch

Retrieve the formatted patch for a specific Gerrit change revision; returns base64-encoded content unless raw output is requested.

Instructions

Returns the formatted patch of a revision (base64-encoded unless the raw content type is requested).

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

Input Schema

NameRequiredDescriptionDefault
rawNo
zipNo
pathNo
parentNo
contextNo
downloadNo
change-idYes
revision-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 disclosure burden. It does add real behavioral detail by stating the response is base64-encoded unless a raw content type is requested, which is useful for handling the result. It says nothing about permissions, size limits, or how the optional parameters affect behavior, leaving significant gaps.

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 sentence with the key information front-loaded and no filler. The parenthetical encoding caveat is well placed. It is efficient, though it is arguably too short for an 8-parameter tool.

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 return-value explanation is not required, and the encoding note covers the main output nuance. However, for a tool with 8 parameters at 0% schema coverage and no annotations, the description is too thin to let an agent invoke it correctly beyond the required IDs.

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 8 parameters, so the description must compensate and largely does not. The mention of raw content type loosely gestures at the 'raw' parameter, but zip, path, parent, context, and download are entirely unexplained in both schema and description. Only the two required path identifiers are self-evident from their names.

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 returns the formatted patch of a revision. That is concrete enough for an agent to know what it gets back. It does not distinguish itself from nearby siblings such as the file-level diff or archive endpoints, so it falls 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 when-to-use guidance and no mention of alternatives. An agent cannot tell from the description whether to call this or the per-file diff endpoint. The only implied usage is 'you want a patch', which the name already conveys.

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