Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidpreferencesedit

getAccountsAccountIdPreferencesEdit

Retrieves a user's edit preferences by account ID, enabling callers to inspect Gerrit edit settings before performing revision reviews.

Instructions

Retrieves the edit 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": "getAccountsAccountIdPreferencesEdit"
  }
}

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.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. 'Retrieves' implies a read-only operation, but nothing is said about auth requirements, whether 'edit preferences' means draft-edit defaults or notification settings, or what the payload contains — and an output schema exists, so the omission of behavior is the real gap.

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 short, front-loaded sentence with no wasted words. Its brevity is appropriate structurally, though it borders on under-specification given the surrounding gaps.

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?

For a tool with an output schema the return value needn't be described, but the undefined domain term 'edit preferences' and the total absence of parameter documentation make the definition insufficient for correct invocation. It is also silent on how it differs from the closely named sibling endpoints.

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%, so the description should explain the sole parameter. The phrase 'of a user' weakly hints that account-id identifies the user, but it never states the expected format (UUID vs username) or that it is required, leaving the parameter effectively undocumented across both fields.

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?

States a specific verb ('Retrieves') and resource ('edit preferences of a user'), so an agent knows it is a read of a preference sub-resource. It does not distinguish itself from the near-identical siblings getAccountsAccountIdPreferences and getAccountsAccountIdPreferencesDiff, so the agent cannot tell which of the three to pick from the description 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, no exclusions, and no reference to alternatives such as the base preferences or diff endpoints. The agent must infer from the name that this is a variant of the preferences family.

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