Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigservercaches

getConfigServerCaches

Lists Gerrit server caches, including plugin-defined caches, to inspect available caches and optional disk statistics.

Instructions

Lists the caches of the server. Caches defined by plugins are included.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getConfigServerCaches"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo
include-diskstatsNo

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 exist, so the description carries the full burden. It usefully discloses that plugin caches appear in the result, but says nothing about permissions, whether the call is a cheap read, pagination, or the shape/volume of what comes back. For a low-risk read listing this is adequate but thin.

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?

Two short sentences with the resource and the key scoping detail (plugin caches) front-loaded; nothing is wasted or repetitive.

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?

With no annotations, no output schema, and undocumented parameters, the definition leaves too much unspecified for correct invocation: the meaning and allowed values of 'format' and the effect of 'include-diskstats' are absent from both schema and description.

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 parameters, so the description must compensate and does not. 'format' and 'include-diskstats' remain opaque — notably 'format' could mean output serialization or cache key format — leaving the agent to guess acceptable values and effects.

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 the caches of the server') and adds scope detail that plugin-defined caches are included. It implicitly distinguishes itself from the singular getConfigServerCachesCacheId by describing a listing, but never names the sibling or draws the contrast explicitly.

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?

No when-to-use guidance is given. An agent must infer that this is for enumerating caches rather than fetching one by id; there is no mention of prerequisites, exclusions, or when to prefer the CacheId sibling.

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