Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidstatus

getAccountsAccountIdStatus

Retrieves the current status of a specified Gerrit account by account ID, helping you verify account state before performing reviews or other operations.

Instructions

Retrieves the status of an account.

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

Input Schema

NameRequiredDescriptionDefault
account-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

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, and it discloses essentially nothing beyond the fact of a read. It does not state whether the caller needs authentication or specific scopes, what a missing/inactive account returns, or whether the status reflects enabled/disabled state. An output schema exists, so return shape need not be spelled out, but operational behavior remains undocumented.

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 padding or redundancy, so it is efficiently sized. However, the brevity comes at the cost of substance — nothing is front-loaded because there is nothing beyond the bare action statement.

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?

The output schema covers return values, so the description need not explain the response, and a single-parameter read is intrinsically simple. Still, given several closely named status/state/active siblings, the definition is not complete enough to drive correct selection without opening schemas.

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?

There is one parameter with 0% schema description coverage, so the description must compensate. The phrase "of an account" weakly implies that account-id identifies the target account, but adds no format, source of the id, or accepted value guidance. That is well short of what a single undocumented required parameter needs.

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 specific verb and resource ("Retrieves the status of an account"), which is clearer than the title restatement but still leaves ambiguity: the sibling set contains both getAccountsAccountIdStatus and getAccountsAccountIdState, plus getAccountsAccountIdActive, and the description does nothing to distinguish "status" from "state" or "active". An agent cannot confidently pick among 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?

No when-to-use guidance, no prerequisites, and no mention of alternative tools. The only implied context is that an account-id is needed. The presence of a near-identical sibling (getAccountsAccountIdState) makes the absence of routing guidance a real gap rather than a minor omission.

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