Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigserverpreferences

getConfigServerPreferences

Fetch the default user preferences for a Gerrit server to establish baseline settings before configuring or comparing user-specific options.

Instructions

Returns the default user preferences for the server.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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. "Returns" weakly implies a read-only, non-mutating call, and "default" hints that inherited server-level values are returned rather than account-specific ones, but there is no statement about permissions required, whether defaults are resolved or raw, or how this interacts with the Edit sibling.

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 front-loaded sentence with no padding or redundant restatement of the title. It is efficient, though the terseness is what leaves the sibling-differentiation gap unaddressed.

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 zero-parameter read tool with an output schema already describing return values, the description is minimally sufficient. The missing piece is relational context: an agent seeing six adjacent preference-related tools has no basis from this sentence to know why this one exists separately from the Diff and Edit variants.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies no input is needed to identify the server context.

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?

"Returns the default user preferences for the server" names a clear verb (returns) and a specific resource (server-level default user preferences), which is more precise than the near-tautological title. It does not, however, distinguish this tool from close siblings such as getConfigServerPreferencesDiff or getAccountsAccountIdPreferences, leaving the agent to infer the difference.

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 choose this tool over the Diff, Edit, or per-account preference variants that sit right next to it. The only usable signal is the word "default," which implies this is the baseline rather than an override, but that is inference rather than stated guidance.

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