Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidgpgkeysgpgkeyid

getAccountsAccountIdGpgkeysGpgKeyId

Retrieves a user's GPG key by account ID and GPG key ID, enabling verification or inspection of the public key associated with a Gerrit account.

Instructions

Retrieves a GPG key of a 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>",
      "gpg-key-id": "<gpg-key-id>"
    },
    "name": "getAccountsAccountIdGpgkeysGpgKeyId"
  }
}

Input Schema

NameRequiredDescriptionDefault
account-idYes
gpg-key-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 it only implies a read operation. It says nothing about permissions required to read a user's GPG key, what happens when the account or key ID does not exist, or any sensitivity of the returned key material.

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?

It is a single front-loaded sentence with no wasted words, but its brevity reflects under-specification rather than discipline. Nothing extra is said because nothing extra is said at all.

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?

Minimum viable. The output schema exists and covers return values, so the description's job is operation selection and parameter meaning, both of which are thin. For a two-parameter read getter this is borderline adequate, though the 0% schema coverage leaves real gaps. Correcting to 3 for consistency with the parameter and transparency gaps accumulated across dimensions.

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 two required string parameters, so the description must compensate and does not. 'Of a user' loosely gestures at account-id but never explains that account-id is the user's account identifier or that gpg-key-id identifies the specific key.

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?

The description names a specific verb and resource ('Retrieves a GPG key'), which lets an agent identify the operation. However, 'of a user' is vague and never mentions the account or the key identifier, and it does not distinguish this singular getter from the sibling getAccountsAccountIdGpgkeys list operation.

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 tool versus the listing sibling, and no stated prerequisites or error conditions. The agent must infer from the name alone that this fetches one key by ID.

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