Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidfilesfileidcontent

getChangesChangeIdRevisionsRevisionIdFilesFileIdContent

Retrieves the content of a specific file at a given change revision in Gerrit for review or inspection.

Instructions

Gets the content of a file from a certain 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>",
      "file-id": "<file-id>"
    },
    "name": "getChangesChangeIdRevisionsRevisionIdFilesFileIdContent"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentNo
file-idYes
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?

With no annotations, the description carries the full behavioral burden. 'Gets' implies a read operation, but the description does not disclose authentication requirements, whether content is returned raw or encoded, error behavior for missing files or revisions, or any other operational detail. The presence of an output schema helps with return values but not with invocation behavior.

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, front-loaded sentence with no unnecessary wording. It is concise, though its brevity contributes to under-specification rather than clarity.

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?

The tool has four parameters with no schema descriptions, no annotations, and an output schema. While the output schema removes the need to describe return values, the description is still far too thin to explain how to invoke the tool correctly or how it differs from nearby file-content tools.

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 all four parameters. The description vaguely associates 'revision' and 'file' with the operation but does not explain the roles of change-id, revision-id, file-id, or the optional parent parameter. It adds almost no meaning beyond the parameter 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 states a specific verb and resource: 'Gets the content of a file from a certain revision.' This clearly identifies the operation as retrieving file content at a given revision. It does not distinguish itself from siblings such as Download, Diff, or Blame, which also operate on file content, 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 guidance on when to use this tool versus alternatives like downloading, diffing, or blaming the same file. The description only implies usage from the verb 'Gets' and gives no exclusions or conditions for selection.

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