Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidreviewersreviewerid

getChangesChangeIdReviewersReviewerId

Retrieves a specific reviewer's record for a Gerrit change using change ID and reviewer ID, so you can confirm review assignments and check reviewer status.

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

Input Schema

NameRequiredDescriptionDefault
change-idYes
reviewer-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 behavioral burden, yet it says nothing about permissions, whether a deleted/inactive reviewer is still returned, or error behavior for unknown IDs. 'Retrieves' implies a read but discloses no further operational traits.

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, so it is concise. But the terseness is under-specification rather than efficiency; there is room to add clarifying detail without bloat.

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 needn't be explained, but the definition still omits which ID format the path segments expect and how this endpoint differs from the several closely named reviewer siblings. For a namespaced REST-style getter with four reviewer variants, that is not enough.

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 coverage is 0%, so both parameters are undocumented, and the description makes no attempt to compensate. It does not clarify whether change-id is a numeric change number or an opaque ID string, nor whether reviewer-id is an account ID, username, or email — all of which matter for correct invocation.

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 states a specific verb and resource: 'Retrieves a reviewer of a change.' An agent knows it returns a single reviewer object rather than a list. However, it does not distinguish this from the revision-scoped sibling getChangesChangeIdRevisionsRevisionIdReviewersReviewerId, which the name alone doesn't disambiguate.

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 versus the revision-scoped reviewer endpoint or the list endpoint getChangesChangeIdReviewers. No prerequisites, 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