Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidcommitscommitidfiles

getProjectsProjectIdCommitsCommitIdFiles

List files modified, added, or deleted in a specific Gerrit commit to review the exact changes and validate a revision.

Instructions

Lists the files that were modified, added or deleted in a commit.

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": {
      "project-id": "<project-id>",
      "commit-id": "<commit-id>"
    },
    "name": "getProjectsProjectIdCommitsCommitIdFiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentNo
commit-idYes
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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. It only indicates that added, modified and deleted files are all included; it says nothing about pagination, result ordering, whether deleted files appear without content, or permission implications for a read against a private project.

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 well-formed sentence with the key qualifier ('modified, added or deleted') front-loaded and no filler. It is efficient, though its brevity is also the source of the missing detail rather than a virtue in itself.

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 values need not be described. However, with an undocumented 'parent' parameter and no pointer toward the content or diff siblings, the definition is only minimally sufficient for an agent to call this correctly in the commit-inspection workflow.

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 three parameters, so the description needed to compensate and does not. In particular the optional 'parent' integer is completely unexplained — an agent cannot tell whether it selects a parent commit for comparison or affects which files are returned.

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 uses a specific verb plus resource ('Lists the files that were modified, added or deleted in a commit'), which is far clearer than the tautological title. It implicitly separates this metadata listing from the sibling content/diff endpoints, but never names those siblings, so the differentiation is left to inference.

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 call this versus getProjectsProjectIdCommitsCommitIdFilesFileIdContent or ...FileIdDiff, nor any mention of prerequisites such as access requirements. The agent must guess the routing from the name alone.

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