Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidpreferences

getAccountsAccountIdPreferences

Retrieve a Gerrit account's user preferences by account ID to review settings such as display and notification options before making changes.

Instructions

Retrieves the user's preferences.

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

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 burden. "Retrieves" implies a read operation, but nothing is said about permission requirements, whether the result is account-scoped or user-scoped, or what happens for accounts the caller cannot access. The only behavioral signal is the implicit read-only nature of 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?

A single short sentence with no wasted words, but it errs on the side of under-specification rather than tightness. There is no structure to speak of because there is only one clause.

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 explained, and only one parameter is required. Still, for a tool whose identity scoping (account vs user) is genuinely ambiguous, one sentence is not enough for an agent to call it confidently without inspecting the schema.

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 parameter account-id has 0% schema description coverage, and the description does not explain its format, whether it is a numeric ID or username, or how it relates to "the user" mentioned in the sentence. This is the one place the description needed to compensate for the schema gap and it 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?

States a verb and resource ("Retrieves the user's preferences"), which is clearer than the name alone, but leaves a real ambiguity: with an account-id parameter required, it is unclear whether this returns the account holder's preferences or the calling user's preferences for that account. It also does nothing to distinguish itself from sibling tools such as getAccountsAccountIdPreferencesDiff, getAccountsAccountIdPreferencesEdit, or getConfigServerPreferences.

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 or authentication, and no routing to related tools like the diff or edit variants. The agent must infer usage purely from the tool 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