Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidcommitscommitiddiff

getProjectsProjectIdCommitsCommitIdDiff

Lists files that differ between two commits, enabling comparison across changes like a pull request diff.

Instructions

Lists the files that differ between two commits. This is useful for comparing commits across multiple changes (similar to a pull request diff).

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

Input Schema

NameRequiredDescriptionDefault
baseNo
commit-idYes
name-onlyNo
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It implies a read ('Lists') but does not confirm read-only semantics, does not explain whether the response is a name list or full diff payload despite the 'Diff' in the name, and does not mention pagination, size limits, or auth requirements.

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?

Two short sentences, front-loaded with the core behavior and followed by a usage hint. No filler or redundancy, though the second sentence is the weaker of the two.

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. However, for a four-parameter, annotation-free tool with zero schema coverage, the definition leaves both the base/commit-id pairing and the name-only flag unexplained — gaps an agent must guess at before calling it correctly.

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 four parameters, so the description must compensate and largely does not. It never explains what 'base' means (presumably the comparison commit, but that is inference), what 'name-only' toggles, or how project-id scopes the lookup.

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: 'Lists the files that differ between two commits', with the analogy 'similar to a pull request diff'. It is clear what the tool returns, though it does not distinguish itself from the sibling per-file diff tool (getProjectsProjectIdCommitsCommitIdFilesFileIdDiff), which an agent could easily confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'This is useful for comparing commits across multiple changes' implies a usage context but is framed as a benefit rather than a condition. There is no statement of when to prefer this over the sibling per-file diff tool, no prerequisites, and no exclusion criteria.

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