Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidbranchesbranchidvalidationoptions

getProjectsProjectIdBranchesBranchIdValidationOptions

Retrieves validation options for a specified Gerrit project and branch, helping you determine which checks apply before submitting changes.

Instructions

Retrieves the validation options applicable for the given project and branch.

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

Input Schema

NameRequiredDescriptionDefault
branch-idYes
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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 burden. 'Retrieves' implies a read operation, but nothing is said about permissions, whether the result is branch-specific configuration, caching, or any side effects. The only behavioral hint is the read-ish verb.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity reflects under-specification rather than disciplined concision.

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 return-value detail is not required, and the tool takes only two simple parameters. However, with zero annotation coverage and zero schema description coverage, the description leaves the agent without usage or parameter grounding, which is thin for an otherwise simple tool.

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 both required parameters. The description only restates that a project and branch are needed, adding no meaning such as whether branch-id is a name or numeric ID, or what happens with a nonexistent branch.

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 uses a specific verb ('Retrieves') and a specific resource ('validation options') scoped to a project and branch, so the agent can tell what it returns. It does not explicitly differentiate itself from the similarly named sibling getChangesChangeIdValidationOptions, so it stops short of a 5.

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 statement of when to call this tool, when not to, or which alternative to use (for example, the change-scoped validation-options sibling). The phrase 'applicable for the given project and branch' describes scope but not decision criteria.

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