Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidreviewers

getChangesChangeIdRevisionsRevisionIdReviewers

Lists reviewers for a specified Gerrit change revision, helping you identify who is assigned to review that revision.

Instructions

Lists the reviewers of 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": "getChangesChangeIdRevisionsRevisionIdReviewers"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
revision-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; the verb "Lists" does convey a non-mutating read operation, which is the key behavioral fact here. It says nothing about pagination, permission/visibility requirements, or whether reviewers include pending/removed entries, all of which matter for a review-workflow listing.

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 short sentence with no filler and the subject front-loaded, but it is under-specified rather than concise-and-complete; there is room for one clarifying clause without bloat.

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, and the self-explanatory parameter names limit damage from the 0% schema coverage. Still, for a listing endpoint no pagination behavior or usage routing is given, leaving the definition only minimally adequate.

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% for both required parameters, so the description must compensate and does so only weakly: "of a revision" hints at the revision-id role and "reviewers" scopes the change-id, but neither parameter's expected format (e.g., numeric id vs. change identifier such as project~branch~Change-Id) is clarified.

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?

"Lists the reviewers of a revision" gives a specific verb (Lists) and resource (reviewers of a revision), which separates it from the singular getChangesChangeIdRevisionsRevisionIdReviewersReviewerId and from the change-level getChangesChangeIdReviewers. It does not explicitly name those siblings, so differentiation is inferred from the phrase "of a revision" rather than stated.

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 the reviewer-by-id sibling or the change-level reviewers endpoint, and no stated prerequisites such as whether the change/revision must be visible to the caller. The agent must infer usage purely 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