Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigserversummary

getConfigServerSummary

Retrieves a summary of the current Gerrit server state, optionally including JVM details, to help monitor configuration and runtime status.

Instructions

Retrieves a summary of the current server state.

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

Input Schema

NameRequiredDescriptionDefault
jvmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 behavioral burden, yet it discloses nothing about what the summary contains, whether it is a cheap or expensive call, or any permission requirements. An output schema exists, which relieves it of describing return values, but the mutation/read profile and content scope remain unstated.

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

Conciseness3/5

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

One short, front-loaded sentence with no wasted words, but the brevity comes at the cost of substance rather than reflecting efficient communication of a complete idea.

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 covers return values, but for a tool whose only parameter is undocumented and whose scope overlaps several siblings, the definition leaves too much unresolved. It needs at least a note on what the summary covers and what the 'jvm' flag does.

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 the single parameter 'jvm' is never mentioned in the description. Its meaning (whether to include JVM-level details) is entirely opaque and must be inferred from the bare property name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb and resource ('Retrieves a summary of the current server state'), but the scope is vague. With siblings such as getConfigServerInfo, getConfigServerVersion, and getConfigServerCapabilities, an agent cannot tell from this text what distinguishes 'summary' from 'info' or 'version'.

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 prerequisites, and no reference to any alternative tool. The agent must guess whether this or getConfigServerInfo is the right call.

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