Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigservermetrics

getConfigServerMetrics

Lists Gerrit server metrics and returns metric-name-to-MetricInfo mappings, optionally filtered by prefix or limited to data-only values.

Instructions

Lists the metrics of the server, returning a map of metric name to a MetricInfo entity.

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

Input Schema

NameRequiredDescriptionDefault
prefixNo
data-onlyNo

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. 'Lists' implies a read-only operation and the return shape is disclosed, but nothing is said about authorization requirements, response size, pagination, or whether the call can be expensive on a large server.

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 well-formed sentence with the verb and return format front-loaded and no filler. It is efficient, though it spends its only clause on return shape while omitting the parameters that matter more.

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 re-explained, but for a tool with two undocumented parameters, no annotations, and a sibling that fetches a single metric, the description leaves too much unresolved 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%: neither 'prefix' nor 'data-only' is explained anywhere. The description never mentions that results can be narrowed by a name prefix or that 'data-only' toggles whether metric payloads are included, leaving both parameters semantically opaque.

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 and resource ('Lists the metrics of the server') and adds the return shape ('map of metric name to a MetricInfo entity'), which clearly separates it from the by-id sibling getConfigServerMetricsMetricId. It does not name any sibling explicitly, so differentiation is inferred rather than stated.

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 when-to-use guidance, no mention of when to prefer getConfigServerMetricsMetricId, and no prerequisites or exclusion conditions. Usage is only weakly implied by the verb 'Lists'.

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