Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeiddetail

getChangesChangeIdDetail

Retrieve a Gerrit change with labels, detailed label data, detailed accounts, reviewer updates, and messages to inspect review status and discussion history.

Instructions

Retrieves a change with labels, detailed labels, detailed accounts, reviewer updates, and messages.

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": {
      "change-id": "<change-id>"
    },
    "name": "getChangesChangeIdDetail"
  }
}

Input Schema

NameRequiredDescriptionDefault
ONo
oNo
change-idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden, yet it discloses only the set of embedded fields. It says nothing about authentication/permission requirements, whether missing changes raise errors, whether output is large (justifying the "Detail" variant), or how pagination/expansion behaves.

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 short sentence, front-loaded with the verb and resource, with no redundant wording. Its brevity crosses into under-specification, but there is no structural waste to penalize.

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?

For a tool with no annotations, no output schema, and three undocumented parameters (two of them opaque single letters), the description is far too thin. An agent still lacks almost everything needed to call it correctly beyond knowing it fetches a change.

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

Parameters1/5

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

Three parameters exist at 0% schema description coverage, including the cryptic "O" and "o", and the description does not mention any of them. Nothing explains what "O", "o", or "change-id" mean or accept, so the description adds no semantics whatsoever over an undocumented schema.

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?

"Retrieves a change" gives a clear verb and resource, and the enumeration of labels, detailed labels, detailed accounts, reviewer updates and messages hints at an expanded/embedded representation. However, the description never distinguishes this from the sibling getChangesChangeId, so an agent cannot tell what "Detail" adds relative to the base fetch.

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 statement of when to use this tool versus getChangesChangeId or the many narrower siblings (getChangesChangeIdMessages, getChangesChangeIdReviewers, etc.). No prerequisites, permissions, or exclusions are mentioned; the agent must infer everything.

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