Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidcapabilitiescapabilityid

getAccountsAccountIdCapabilitiesCapabilityId

Checks whether a specified Gerrit account holds a given global capability, helping verify user permissions before granting access or performing actions.

Instructions

Checks if a user has a certain global capability.

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>",
      "capability-id": "<capability-id>"
    },
    "name": "getAccountsAccountIdCapabilitiesCapabilityId"
  }
}

Input Schema

NameRequiredDescriptionDefault
account-idYes
capability-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only implies a read via 'Checks'. It does not say whether a missing capability yields an error or a falsy result, whether the caller needs admin rights, or that the check is against global rather than project-scoped capabilities in any operational sense.

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 sentence with the key concept front-loaded and no wasted words. It is efficient, though its brevity edges toward under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is structurally simple (two string params) and an output schema exists, so return values need not be described. The remaining gaps are parameter formats and the semantics of a failed check, which are modest for a tool of this complexity.

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 both required parameters, so the description must compensate and does not: it never explains that 'account-id' may be a numeric ID, username, or 'self', nor that 'capability-id' is a capability name string. The mapping from 'a user' and 'a certain global capability' to the two params is only inferable.

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 specific verb ('Checks') and resource ('a certain global capability') applied to a user, which is enough to distinguish it from the list-style sibling getAccountsAccountIdCapabilities. It stops short of naming any sibling or stating that this is a single-capability membership test rather than a capability lookup.

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 use this tool versus getAccountsAccountIdCapabilities or the config-level getConfigServerCapabilities. No prerequisites, no exclusions, and no note on what a negative result means.

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