Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidavatarchangeurl

getAccountsAccountIdAvatarChangeUrl

Retrieve the URL where a specified Gerrit account can change its avatar image.

Instructions

Retrieves the URL where the user can change the avatar image.

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

Input Schema

NameRequiredDescriptionDefault
account-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 discloses almost nothing beyond the returned artifact. It does not say whether the operation is read-only (implied but unstated), what permissions are required to request a change URL, whether the URL is short-lived or single-use, or what the caller should do with it.

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 tight sentence with the outcome front-loaded and no filler. It is appropriately sized, though the brevity contributes to the specification gaps noted elsewhere.

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?

An output schema exists, so return-value explanation is not required, but the tool still lacks annotations, an undocumented required parameter, and no differentiation from the closely named sibling getAccountsAccountIdAvatar. For even a simple endpoint, the definition leaves the agent guessing about scope and permissions.

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 the single required 'account-id' parameter, and the description never mentions it. There is no clarification of whether the ID is a numeric account ID, a username, or whose account scope the URL is generated for, so the description fails to compensate for the schema gap.

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 clear verb ('Retrieves') and a specific resource ('the URL where the user can change the avatar image'), which is more precise than the tautological title. However, it does not distinguish itself from the sibling getAccountsAccountIdAvatar, which an agent could easily confuse with this tool given the near-identical naming.

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 rather than getAccountsAccountIdAvatar or the other avatar-adjacent account tools, and no prerequisites or context are stated. The agent must infer the use case entirely from the one-line purpose.

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