Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidreviewersrevieweridvotes

getChangesChangeIdReviewersReviewerIdVotes

Retrieve the votes cast by a specific reviewer on a Gerrit change by supplying the change ID and reviewer ID.

Instructions

Lists the votes for a specific reviewer of the 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": "getChangesChangeIdReviewersReviewerIdVotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
reviewer-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 burden and discloses very little. 'Lists' implies a read-only, non-destructive operation, but it says nothing about permissions, pagination, behavior on an unknown reviewer-id, or what happens when a reviewer has no votes.

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 short sentence with the resource and scope front-loaded; nothing is wasted. It is arguably under-specified rather than verbose, but it is efficiently structured.

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?

The tool is simple with only two required parameters and an output schema that documents return values, so the description needn't explain results. However, for a tool with zero annotation coverage and no schema descriptions, it leaves out behavioral and parameter detail an agent would benefit from.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does map both parameters loosely to entities ('the change' and 'the specific reviewer'), which is some help, but it adds no format, identifier syntax, or path-context detail for either required parameter.

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 gives a specific verb and resource ('Lists the votes') scoped to 'a specific reviewer of the change', which distinguishes it from siblings like getChangesChangeIdReviewers or getChangesChangeIdReviewersReviewerId. It is clear what the tool returns without opening the schema, though it does not explicitly contrast 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 when-to-use guidance, no mention of prerequisites, and no reference to an alternative tool for retrieving reviewer data or vote details. The agent must infer that this is the narrow per-reviewer vote listing rather than the broader reviewer listing.

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