Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigserverindexesindexidversionsindexversionid

getConfigServerIndexesIndexIdVersionsIndexVersionId

Retrieve details for a specific version of a Gerrit index by providing its index ID and version ID, useful for inspecting index version metadata and configuration.

Instructions

Get info about one version 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>",
      "index-version-id": "<index-version-id>"
    },
    "name": "getConfigServerIndexesIndexIdVersionsIndexVersionId"
  }
}

Input Schema

NameRequiredDescriptionDefault
index-idYes
index-version-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'Get info' implies a read-only operation, but the description says nothing about permissions, error behavior for missing indexes, or authentication requirements. The output schema covers the return shape, which limits the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no redundant or filler wording. Its brevity suits a simple single-resource read tool, even though other dimensions need more content.

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 exists, so return values need not be described. However, with no annotations and 0% schema description coverage, the definition leaves both required parameters and the tool's operational context unexplained, which is not sufficient for an agent to call it confidently.

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%, and both required parameters ('index-id' and 'index-version-id') are undocumented in the schema. The description only vaguely implies the two concepts through 'one version of an index' and adds no format, source, or meaning for either 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 states a specific verb ('Get info') and resource ('one version of an index used by Gerrit'), so an agent can distinguish it from the sibling version-list and index-level tools. It stops short of explicitly naming those alternatives.

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 rather than the sibling list or index tools, and no stated prerequisites or exclusions. The only signal is the name and the phrase 'one version,' which implies retrieval of a single item.

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