Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidarchive

getChangesChangeIdRevisionsRevisionIdArchive

Retrieves an archive of the files in a specified Gerrit change revision using the change ID and revision ID, enabling download or inspection of revision contents.

Instructions

Retrieves an archive of the files in 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": "getChangesChangeIdRevisionsRevisionIdArchive"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo
change-idYes
revision-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

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 exist, so the description carries the full disclosure burden, and it discloses almost nothing. It does not say the response is a binary archive blob rather than JSON, which formats are supported, whether there is a size cap, or what permissions are required for a given change. That last point matters because the effect of this call depends on the account's access to the change.

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 wasted words. Its brevity is a virtue structurally, though it reflects 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?

For a tool with no annotations, three undocumented parameters, and a non-JSON return, the definition is too thin. An output schema exists, so return-shape explanation is not required, but the binary nature of the payload and the format enumeration are exactly the kind of details the description should supply and does not.

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. 'In a revision' loosely implies the change-id and revision-id pair as a locator, but the format parameter — the one real choice the caller makes and the one that determines the archive encoding — is never mentioned in the description or the schema. The description therefore does not compensate for the coverage gap.

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: 'Retrieves an archive of the files in a revision.' This is clear enough to distinguish a bulk archive download from the many per-file siblings such as FilesFileIdContent or FilesFileIdDownload. It stops short of explicitly naming an alternative, so it sits at 4 rather than 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, no mention of when to prefer this over getChangesChangeIdRevisionsRevisionIdFiles, and no note of prerequisites or limits. The agent is left to infer everything about selection from the one-line purpose statement.

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