Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidreviewersreviewerid

getChangesChangeIdRevisionsRevisionIdReviewersReviewerId

Retrieve a reviewer's details for a specific Gerrit change revision by supplying change, revision, and reviewer IDs.

Instructions

Retrieves a reviewer of a change.

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>",
      "reviewer-id": "<reviewer-id>"
    },
    "name": "getChangesChangeIdRevisionsRevisionIdReviewersReviewerId"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
reviewer-idYes
revision-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

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?

With no annotations supplied, the description carries the full behavioral burden and discloses almost nothing: not whether the call is read-only (implied but unstated), not what happens when a reviewer-id is invalid for the revision, and not what permissions are needed. The only behavioral fact conveyed is that exactly one reviewer is returned.

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?

The definition is one short, front-loaded sentence with no filler, so nothing is wasted. The problem is under-specification rather than verbosity, which caps this dimension at an adequate level.

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-value shape need not be explained, but for a tool requiring three path parameters with zero schema documentation and no annotations, the description is too thin. An agent cannot tell from this text how to construct the request against the right revision scope.

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% and the description adds no meaning for any of the three required parameters. It does not explain that change-id and revision-id form a hierarchical locator, nor that revision-id may accept special values such as 'current', which is exactly the kind of detail the schema omits.

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 single sentence states a verb and resource ('Retrieves a reviewer of a change'), which is enough to know it returns one reviewer record rather than the reviewer list handled by the sibling getChangesChangeIdRevisionsRevisionIdReviewers. However, it never clarifies whether the reviewer is identified per revision or per change, nor distinguishes it from getChangesChangeIdReviewersReviewerId, which appears to do nearly the same thing at change scope.

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 prerequisites, and no mention of the closely related sibling tools that list reviewers or fetch reviewer votes. The agent must infer the selection rule purely from the long path-style tool 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