Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigserverpreferencesdiff

getConfigServerPreferencesDiff

Retrieves the Gerrit server's default diff preferences so reviewers can apply consistent comparison settings when inspecting changes.

Instructions

Returns the default diff 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": "getConfigServerPreferencesDiff"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 supplied, so the description carries the disclosure burden. It implies a safe read-only retrieval of default settings, but it does not confirm read-only behavior, state whether authentication is required, or clarify whether defaults are global or fallback values. For a zero-parameter getter with an output schema, 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?

The description is a single front-loaded sentence with no filler. It states the resource and the result efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a zero-parameter read tool with an output schema, the description is nearly complete: the return shape is documented elsewhere, and no inputs need explanation. The only remaining gap is that 'default' is not clarified in terms of scope, such as server-wide versus fallback preferences.

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 no parameters, so there is no parameter semantics to explain. The baseline for a zero-parameter tool is 4, and the description introduces no confusing parameter language.

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: returning the server's default diff preferences. It is clear enough to distinguish from the general getConfigServerPreferences sibling by the word 'default', but it does not explicitly contrast itself with getConfigServerPreferencesEdit or the account-level diff preferences endpoint.

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 about when to use this tool rather than getConfigServerPreferences, getConfigServerPreferencesEdit, or getAccountsAccountIdPreferencesDiff. The description leaves the agent to infer usage from the name and the sibling names alone.

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