Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidfiles

getChangesChangeIdRevisionsRevisionIdFiles

Lists files added, modified, or deleted in a specific Gerrit change revision, so you can inspect what a patch set touched before reviewing or merging.

Instructions

Lists the files that were added, modified, or deleted 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": "getChangesChangeIdRevisionsRevisionIdFiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
baseNo
parentNo
reviewedNo
change-idYes
revision-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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 are provided, so the description carries the full burden. It conveys read-only listing behavior and the file-state categories, but says nothing about pagination, filtering effects of the four optional parameters, permissions, or ordering. For a six-parameter Gerrit endpoint with zero annotation coverage this is thin.

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 clean, front-loaded sentence with no wasted wording, which is good. However, the brevity is under-specification rather than economy, given the parameter surface it must cover.

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 structure need not be described. But with four undocumented optional filters, no annotations, and no guidance on invocation context, the description does not close the gap for a tool of this complexity.

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 six parameters, and the description explains only the implicit role of change-id and revision-id. The meaning of q, base, parent, and reviewed — all non-obvious Gerrit query modifiers — is left completely undocumented in both schema and description.

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?

States a specific verb ('Lists') and resource ('the files') scoped to a revision, and specifies the file states returned (added, modified, deleted). It does not differentiate this list endpoint from siblings such as getChangesChangeIdRevisionsRevisionIdFilesFileIdContent or ...Blame, so an agent must infer from the name alone that those operate on a single file.

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 alternatives (e.g., the per-file content/diff/blame siblings), and no stated preconditions such as required permissions or whether the revision must be current. The only implicit usage signal is that it is a listing operation over a revision.

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