Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidfilesfileiddownload

getChangesChangeIdRevisionsRevisionIdFilesFileIdDownload

Download a file's content from a specific Gerrit revision in a safe, non-executable format to inspect untrusted code without risk of execution.

Instructions

Downloads the content of a file from a certain revision, in a safe format that poses no risk for inadvertent execution of untrusted code.

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

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.9/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 burden. It does disclose one useful behavioral trait: the returned content is in a safe format that cannot be inadvertently executed when the file is untrusted code. It says nothing about permissions, size limits, or how binary files are handled.

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?

It is a single, front-loaded sentence that wastes no words. The only inefficiency is that concision comes at the cost of coverage; nothing is redundant, but little is said.

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?

An output schema exists, so return values need not be described. Even so, a four-parameter mutation-free download tool with no annotations needs more than one sentence: parameter meanings and the distinction from the Content sibling are missing.

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 four parameters, and the description only implicitly references file-id and revision-id through 'file' and 'revision'. The change-id and parent parameters are never explained, so the description does little to compensate for the unlabeled schema.

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 gives a specific verb and resource: 'Downloads the content of a file from a certain revision.' It adds a scope qualifier about a safe, non-executable format. However, it does not distinguish this from the sibling getChangesChangeIdRevisionsRevisionIdFilesFileIdContent, which an agent would likely consider equivalent without more information.

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 about when to use this tool rather than the Content, Diff, Blame, or Archive siblings, and no prerequisites are stated. The agent must infer from the name alone that this is the download variant.

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