Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidreviewers

getChangesChangeIdReviewers

Lists the reviewers of a Gerrit change as ReviewerInfo entities, helping users inspect who is involved in reviewing a specific change.

Instructions

Lists the reviewers of a change as ReviewerInfo entities.

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>"
    },
    "name": "getChangesChangeIdReviewers"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

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, yet it says nothing about pagination, permission requirements, whether voting data or reviewer state is included, or what happens for a nonexistent change-id. Beyond naming the returned entity type, it adds no behavioral context for what is a read of potentially large, sensitive review data.

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?

One short sentence with the resource and return type front-loaded and no filler. It is efficient, though its brevity borders on under-specification rather than genuine conciseness.

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 the ReviewerInfo structure need not be re-explained. However, for a tool embedded in a dense family of reviewer-related endpoints, the definition omits the change-level vs. revision-level scope and how this differs from getting a single reviewer or their votes, leaving a real gap.

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 the single required 'change-id' parameter, and the description says nothing about its format (numeric ID vs. project~branch~changeId triple) or how it relates to the sibling tools that take revision IDs. The description does not compensate for the schema gap.

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 ('Lists') and resource ('the reviewers of a change'), and names the entity type returned (ReviewerInfo). It is clear what the tool does, but it does not distinguish itself from siblings like getChangesChangeIdRevisionsRevisionIdReviewers or getChangesChangeIdReviewersReviewerId, which an agent must otherwise infer from names alone.

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 alternatives. The agent is left to guess that this covers change-level reviewers only, while revision-level reviewers and reviewer votes live in sibling tools.

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