Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidcommit

getChangesChangeIdRevisionsRevisionIdCommit

Retrieves a Gerrit revision's commit as a CommitInfo entity, enabling inspection of commit details for a specific change and revision.

Instructions

Retrieves the commit of a revision as a CommitInfo entity.

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

Input Schema

NameRequiredDescriptionDefault
linksNo
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. 'Retrieves' implies a read-only operation, which is useful, but there is nothing about required permissions, behavior for unknown change/revision IDs, or whether the commit is fetched from the API or derived. Most of the behavioral surface is left undisclosed.

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 resource and return type front-loaded; nothing is padded. It is terse to the point of under-specification, but not wasteful.

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 explained, but with 0% parameter documentation, an undocumented 'links' flag, and no annotations, an agent cannot confidently construct a call. The definition is too thin for a three-parameter endpoint in a dense revision-API surface.

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. The description never mentions 'change-id', 'revision-id', or the 'links' boolean, so the meaning of the optional links flag and the expected identifier formats are documented nowhere. The description adds essentially no parameter meaning beyond the bare 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?

States a specific verb and resource: retrieves the commit of a revision, and names the return entity (CommitInfo). This is clear enough to distinguish it from sibling endpoints like ...RevisionsRevisionId (the revision itself) or ...RevisionsRevisionIdPatch. It stops short of explicitly contrasting itself with those siblings.

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 tool versus the many sibling revision endpoints, no prerequisites (e.g. change must exist, revision must be current), and no exclusions. The agent must infer usage entirely 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