Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidtokens

getAccountsAccountIdTokens

Lists all token IDs associated with a Gerrit account and returns AuthTokenInfo metadata without exposing plain text tokens.

Instructions

Lists the token ids of an account as a list of AuthTokenInfos. The plain text token will never be returned.

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": "getAccountsAccountIdTokens"
  }
}

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?

With no annotations, the description carries the full behavioral burden. It does usefully disclose that the plain text token is never returned, which sets expectations for the response, but says nothing about required permissions, whether revoked/expired tokens are included, or pagination behavior for accounts with many tokens.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero waste. The functional statement is front-loaded and the security-relevant caveat about the plain text token follows immediately.

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?

The presence of an output schema means return structure need not be described, and the tool is simple (one required parameter). Still, for a credentials-adjacent read, the absence of any note on authorization requirements or token state filtering leaves a meaningful gap.

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 single parameter (account-id) is undocumented in both schema and description. The phrase "of an account" only restates the obvious; it does not clarify whether the value is a numeric account ID, a username, or a formatted identifier, which matters for calling the tool correctly.

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 ("Lists") and resource ("token ids of an account") and names the payload type (AuthTokenInfos), so the agent knows exactly what it retrieves. It does not need to differentiate from a sibling because no other sibling in the provided list deals with tokens, though it makes no explicit contrast either.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the read path for an account's token inventory, but there is no statement of when to prefer it, what prerequisites exist (e.g. whether the caller must be the account owner or admin), or what it should not be used for.

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