Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidstate

getAccountsAccountIdState

Retrieves an account's full state and permissions to help diagnose account access issues and permission problems.

Instructions

Retrieves the superset of all information related to an account. This information is useful to inspect issues with the account and its permissions. The account state is returned as an AccountStateInfo entity.

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

Input Schema

NameRequiredDescriptionDefault
account-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 full burden. It does disclose the returned entity type (AccountStateInfo) and that the response is a broad superset, but it says nothing about permissions required, whether the read is expensive, or any rate limits — notable gaps for a tool that aggregates all account information.

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?

Three short sentences, front-loaded with the core action and followed by the use case and the return type. No filler, though the middle sentence is the weakest link in value density.

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?

An output schema exists, so return values needn't be spelled out, and the description names the entity type anyway. But for a tool sitting among many near-identical account endpoints, the missing differentiation from siblings and the undocumented sole parameter leave real gaps.

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% for the single required 'account-id' parameter, and the description never mentions it at all — no format, source, or whether it accepts an ID versus a username. The parameter is conventional enough to be guessable, but the description does nothing to compensate for the coverage gap.

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 uses a specific verb ('Retrieves') and resource ('all information related to an account'), and the word 'superset' hints at how this differs from narrower siblings like getAccountsAccountIdDetail or getAccountsAccountIdCapabilities. It stops short of explicitly naming the sibling it should be chosen over, so an agent still has to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Useful to inspect issues with the account and its permissions' implies a debugging/diagnostic context, which is genuine when-to-use guidance. However, it gives no exclusions and never names the obvious alternative (getAccountsAccountId for general account data), leaving the agent to guess between several overlapping account endpoints.

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