Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidname

getAccountsAccountIdName

Retrieves the full name of a Gerrit account by account ID, helping you identify users when reviewing changes or querying account details.

Instructions

Retrieves the full name 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": "getAccountsAccountIdName"
  }
}

Input Schema

NameRequiredDescriptionDefault
account-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 disclosure burden and does almost nothing with it. It does not say whether the call requires authentication, what happens if the account has no name set, or whether the result is cached or rate limited. The presence of an output schema covers the return shape, but operational behavior is undocumented.

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?

One short, front-loaded sentence with no filler. It is arguably slightly too terse for a tool with no annotations, but nothing is wasted or buried.

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?

For a simple single-parameter read with an output schema, the essentials are present: what it returns and which account it targets. What is missing is disambiguation between 'full name' and the sibling name/username tools, plus any note on null or missing names, which leaves a small but real gap given zero annotation coverage.

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

Parameters4/5

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

There is a single parameter, account-id, and schema description coverage is 0%, so the description contributes nothing to parameter meaning. However, with only one self-describing identifier parameter and a matching required field in the schema, the definition is not meaningfully deficient here.

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 and resource: 'Retrieves the full name of an account.' This is a clear read operation on an identifiable resource. It stops short of explicitly distinguishing itself from look-alike siblings such as getAccountsAccountIdUsername or getAccountsAccountIdDetail, so the agent must infer the 'full name' vs. 'username' distinction.

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 indication of when to prefer this over getAccountsAccountIdUsername or getAccountsAccountIdDetail, and no stated prerequisites. Usage is only implied by the tool name and the phrase 'full name'.

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