Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeideditchangeeditid

getChangesChangeIdEditChangeEditId

Retrieves the content of a file from a Gerrit change edit, with an optional base version, so you can inspect edited file contents before review.

Instructions

Retrieves content of a file from a change edit.

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>",
      "change-edit-id": "<change-edit-id>"
    },
    "name": "getChangesChangeIdEditChangeEditId"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNo
change-idYes
change-edit-idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it delivers almost nothing: no indication of return encoding (raw vs base64), auth requirements, error behavior for missing edits, or what happens with the 'base' flag. Only the bare fact of a read is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, so nothing is wasted. But it is under-specified rather than tight, and there is no structure beyond the one clause to help an agent scan for prerequisites or scope.

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?

With no annotations, no output schema, and 0% parameter coverage, the definition leaves meaningful gaps for a three-parameter retrieval tool. The narrow purpose is at least stated, keeping it at minimum viable rather than inadequate.

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 the description needed to compensate and does not. It implicitly covers change-id and change-edit-id via 'from a change edit', but the 'base' boolean is entirely unexplained, leaving an agent unable to know what it toggles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb ('Retrieves') and a resource ('content of a file from a change edit'), which is more specific than the title. However, it gives no hint of how it differs from near-identical siblings such as getChangesChangeIdEdit, and 'change edit' remains opaque without domain context.

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 versus getChangesChangeIdEdit or the Meta variant, and no prerequisites (e.g., that an edit must exist or that the caller needs edit access) are mentioned. The agent must infer usage purely from the 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