Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidpreferencesdiff

getAccountsAccountIdPreferencesDiff

Retrieve a user's diff preferences to understand their configured comparison settings before reviewing changes.

Instructions

Retrieves the diff preferences of a user.

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": {
      "account-id": "<account-id>"
    },
    "name": "getAccountsAccountIdPreferencesDiff"
  }
}

Input Schema

NameRequiredDescriptionDefault
account-idYes

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 says nothing about read-only semantics, permissions/auth requirements, or whether the 'diff' is computed against defaults or another user. The only implicit behavior is that it is a retrieval, derived from the verb.

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 filler, so it is efficiently sized. However, the brevity comes at the cost of substance, leaving the core term 'diff preferences' unexplained rather than being genuinely concise.

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 described, but for a tool with zero annotation coverage and an undocumented parameter the description should still clarify what 'diff preferences' are and what account-id identifies. As written, an agent would have to open the output schema to learn what the tool actually returns.

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?

The single required parameter account-id has 0% schema description coverage, and the description only obliquely gestures at it with 'of a user' — it never states that account-id is the user identifier or what format it takes. With coverage this low, the description needed to compensate and does not.

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?

The description has a verb ('Retrieves') and a resource ('diff preferences of a user'), but 'diff preferences' is ambiguous — it could mean a difference between two preference sets or, as in the Gerrit-style siblings, the diff-view preference settings. It does not distinguish this tool from the adjacent getAccountsAccountIdPreferences, so an agent cannot confidently pick between them from the text alone.

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 at all: no mention of when to call this versus getAccountsAccountIdPreferences or getAccountsAccountIdPreferencesEdit, and no prerequisites or exclusions. The agent must infer everything from the name.

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