Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidsuggestreviewers

getChangesChangeIdSuggestReviewers

Suggest reviewers for a Gerrit change by ID, with optional query and limit to narrow candidate reviewers.

Instructions

Suggest the reviewers for a given query q and result limit n. If result limit is not passed, then the default 10 is used.

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": "getChangesChangeIdSuggestReviewers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
change-idYes
exclude-groupsNo
reviewer-stateNo

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full disclosure burden, and it says almost nothing. It does not indicate whether this is a read-only suggestion or whether it writes anything, what permissions are required, how suggestions are ranked or filtered, or what reviewer-state means. Only the limit default (10) is disclosed.

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?

Two short sentences, front-loaded with the core action and no filler. It is efficient, though the brevity comes at the cost of substance rather than being tight around complete information.

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?

The output schema means return values need not be described, but with zero annotation coverage and zero schema description coverage, the description should compensate and does not. Three of five parameters and the whole behavioral profile remain undocumented for a five-parameter tool.

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

Parameters1/5

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

Schema description coverage is 0% across five parameters, and the description only touches two of them (query and limit) without adding types, formats, or accepted values. The required change-id and the exclude-groups and reviewer-state parameters are entirely unexplained anywhere.

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 description gives a specific verb and resource ("Suggest the reviewers") tied to a query and limit, so the basic action is intelligible. However, it never states that suggestions are scoped to a change, nor how this differs from the sibling getChangesChangeIdReviewers, which presumably lists existing reviewers rather than suggesting new ones.

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 tool versus listing existing reviewers, revision-level reviewer endpoints, or the project/branch suggest-reviewers sibling. The only conditional statement concerns the limit default, which is a parameter behavior, not usage guidance.

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