Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidcapabilities

getAccountsAccountIdCapabilities

Retrieve the global capabilities enabled for a specific user account, so you can verify which Gerrit features and permissions that user has access to.

Instructions

Returns the global capabilities that are enabled for the specified 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": "getAccountsAccountIdCapabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
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?

No annotations are supplied, so the description carries the full behavioral burden, yet the only hint is the word 'Returns' implying a read. It says nothing about authentication requirements, whether the result is per-account versus global, what 'global' excludes, or how many capabilities come back. For a tool with zero annotation coverage this is a substantial 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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is part of the reason the parameters and behavior go unexplained.

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 the definition leaves too much open for a two-parameter tool with no annotations: 'q' is undocumented and the account-vs-user wording creates ambiguity about scope. An agent could invoke it, but not confidently.

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%, and the description only glosses the required 'account-id' as 'the specified user', which is arguably misleading since the parameter is an account identifier, not a user. The optional 'q' array parameter is never mentioned at all, so half the surface is undefined in both schema and description.

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 gives a concrete verb ('Returns') and a specific resource ('global capabilities that are enabled for the specified user'), which cleanly separates it from the sibling getAccountsAccountIdCapabilitiesCapabilityId that fetches a single capability. It stops short of explicitly naming that sibling or restating the account scope, so it lands just below a 5.

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 guidance on when to call this versus the per-capability sibling or the other account sub-resources; usage is only inferable from the name. No prerequisites, exclusions, or alternatives are stated.

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