Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigserverindexesindexidversions

getConfigServerIndexesIndexIdVersions

Lists every version of a Gerrit server index so you can identify available index revisions and choose the one needed for inspection or maintenance.

Instructions

Lists versions of an index used by Gerrit.

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": {
      "index-id": "<index-id>"
    },
    "name": "getConfigServerIndexesIndexIdVersions"
  }
}

Input Schema

NameRequiredDescriptionDefault
index-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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 supplied, so the description carries the full burden of behavioral disclosure. "Lists" implies a read-only enumeration, but the description says nothing about pagination, ordering, whether deprecated/offline versions are included, permission requirements, or what 'index' scope means in Gerrit. Only the barest hint of read semantics is conveyed.

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 no filler, and the verb/resource pair is front-loaded. It is efficient but so thin that brevity shades into under-specification rather than disciplined concision.

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 need not be explained. However, for a tool with a required, fully undocumented identifier parameter and no annotations, the definition leaves too much for the agent to infer about argument format and expected results.

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?

The single required parameter index-id has 0% schema description coverage, and the description never mentions it or explains its format. With one undocumented parameter, the description should compensate but does not, so an agent must guess what a valid index-id looks like.

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?

States a specific verb and resource: "Lists versions of an index." The noun "versions" implicitly distinguishes it from the sibling that fetches a single version (getConfigServerIndexesIndexIdVersionsIndexVersionId), though that sibling is never named. "Used by Gerrit" adds domain framing but no further specificity.

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 indication of when to call this versus getConfigServerIndexesIndexId or getConfigServerIndexesIndexIdVersionsIndexVersionId. No prerequisites, no exclusions, no context about what an index version means for the agent's task.

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