Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidrelated

getChangesChangeIdRevisionsRevisionIdRelated

Lists changes related to a specific revision by ancestry, returning a RelatedChangesInfo entity for analyzing change relationships.

Instructions

Lists the changes related to a revision by ancestry as a RelatedChangesInfo entity.

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>",
      "revision-id": "<revision-id>"
    },
    "name": "getChangesChangeIdRevisionsRevisionIdRelated"
  }
}

Input Schema

NameRequiredDescriptionDefault
oNo
change-idYes
revision-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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 disclosure burden. It conveys that the lookup is read-only ('Lists') and that the relation is by ancestry, but says nothing about authentication/permission requirements, whether results include merged or abandoned changes, pagination, or truncation behavior.

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 front-loaded sentence with the verb and scope first and no filler. It is efficient, though its brevity is partly a symptom of under-specification rather than disciplined editing.

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 structure need not be described. However, for a three-parameter read endpoint with zero schema coverage and no annotations, the description omits parameter meaning, option filtering, and access prerequisites, leaving real gaps an agent would have to guess at.

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 three parameters, so the description must compensate and largely does not. 'change-id' and 'revision-id' are only obliquely implied by the nouns in the sentence, and the 'o' options array is never mentioned at all, leaving its accepted string values and effect completely unexplained.

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 specific verb ('Lists') and a precisely scoped resource ('changes related to a revision by ancestry'), and names the return entity type (RelatedChangesInfo). It is not tautological like the title, though it never names a sibling such as getChangesChangeIdRevisionsRevisionId to distinguish the related-changes view from the revision view.

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 or when-not-to-use guidance, and no alternative is mentioned despite dozens of sibling tools under the same change/revision path. The agent must infer that this is the endpoint for ancestry-based related changes rather than, say, files, checks, or review data.

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