Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidbranchesbranchidsuggestreviewers

getProjectsProjectIdBranchesBranchIdSuggestReviewers

Suggest reviewers for a Gerrit project branch using a search query, with optional result limits, reviewer-state filters, and group exclusion; returns 10 results by default.

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": {
      "project-id": "<project-id>",
      "branch-id": "<branch-id>"
    },
    "name": "getProjectsProjectIdBranchesBranchIdSuggestReviewers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
branch-idYes
project-idYes
exclude-groupsNo
reviewer-stateNo

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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. It discloses the default limit of 10, which is useful, but does not clarify that this is a read-only suggestion operation, what permissions may be required, or how results are affected by reviewer-state and exclude-groups.

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?

The description is brief and front-loads the main purpose. The second sentence about the default limit is useful, but the use of shorthand 'q' and 'n' instead of schema parameter names adds avoidable ambiguity.

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 tool has six parameters, no annotations, and no schema parameter descriptions. Although an output schema exists, the description does not sufficiently explain the inputs or usage conditions needed to invoke the tool correctly.

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%, so the description must compensate. It mentions query and limit, but refers to them as 'q' and 'n' rather than the actual 'query' and 'limit' parameters, and it provides no meaning for branch-id, project-id, exclude-groups, or reviewer-state.

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 clearly states that the tool suggests reviewers, which is a specific verb and resource. It does not distinguish this tool from the sibling suggest-reviewers tool getChangesChangeIdSuggestReviewers, and the parameter names it uses ('q' and 'n') do not match the schema.

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?

The description only states the default limit behavior when the limit is not passed. It gives no guidance on when to use this tool versus alternatives such as getChangesChangeIdSuggestReviewers, nor does it explain required context like branch or project scope.

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