Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidgpgkeys

getAccountsAccountIdGpgkeys

Retrieve the GPG keys associated with a Gerrit account by account ID to verify signed commits and inspect the account's published keys.

Instructions

Returns the GPG keys 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": "getAccountsAccountIdGpgkeys"
  }
}

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.9/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 of behavioral disclosure. It implies a read operation via "Returns" but says nothing about pagination, ordering, empty-list behavior, or permission requirements, leaving meaningful gaps for an unpinned tool.

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 wasted words. It is terse rather than padded, though it could have spent one more clause on scope or the single-key alternative at negligible cost.

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?

The output schema exists, so return values need not be explained, and the tool is simple with one parameter. Still, with no annotations and no behavioral or usage context, the definition leaves the agent without enough to decide when this list tool is the right call versus the single-key sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the single parameter (account-id) is self-explanatory and the phrase "of an account" loosely ties it to the input. The description adds little meaning beyond the schema, though there is limited room to add any for an ID parameter.

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?

States a specific verb and resource ("Returns the GPG keys of an account") and the plural "keys" signals a collection, which implicitly separates it from the sibling getAccountsAccountIdGpgkeysGpgKeyId that fetches one key. It stops short of explicitly naming that sibling or clarifying the scope of the account context.

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 when a single-key lookup (the GpgKeyId sibling) would be preferred, and no prerequisites or exclusions. The agent must infer usage purely from the name and the one-line description.

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