Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigservermetricsmetricid

getConfigServerMetricsMetricId

Retrieves a specific Gerrit server metric by its metric ID; URL-encode the ID when the metric name contains slashes.

Instructions

Retrieves a single metric of the server. The metric name is used as the \{metric-id\} and must be URL-encoded because it may contain slashes.

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": {
      "metric-id": "<metric-id>"
    },
    "name": "getConfigServerMetricsMetricId"
  }
}

Input Schema

NameRequiredDescriptionDefault
data-onlyNo
metric-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 behavioral burden. It usefully discloses that metric-id may contain slashes and must be URL-encoded, but it does not explain the data-only flag, error behavior, or explicitly state that the operation is read-only; the output schema covers return values.

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 two sentences with no wasted wording, and the key operational caveat about slashes and URL encoding is front-loaded after the purpose statement.

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?

For a simple getter with an output schema and two parameters, the description covers the central metric-id constraint. However, with no annotations and zero schema coverage it leaves the data-only parameter unexplained and does not explicitly state the read-only nature of the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It gives meaningful semantics for the required metric-id (the metric name, URL-encoded, may contain slashes) but completely omits the optional data-only boolean, leaving one of two parameters undocumented.

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: retrieves a single metric of the server. The word 'single' implicitly distinguishes it from the sibling list tool getConfigServerMetrics, though it does not name that alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The purpose implies this is for fetching one metric by name, but an agent must infer that getConfigServerMetrics is the listing counterpart.

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