Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidin

getChangesChangeIdIn

Retrieves the branches and tags that contain a specific Gerrit change and returns IncludedInInfo, helping identify where the change is included.

Instructions

Retrieves the branches and tags in which a change is included. As result an IncludedInInfo entity is 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": {
      "change-id": "<change-id>"
    },
    "name": "getChangesChangeIdIn"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-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, yet it says nothing about required permissions, whether the change must be merged, what happens for a change with no branch/tag containment, or error behaviour. Naming the IncludedInInfo entity is largely redundant because an output schema already exists.

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?

Two short sentences with the operation stated first and the result second; nothing is padded. The second sentence is close to filler given the output schema, but it does no real harm.

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?

The output schema relieves the description of explaining return values, but for a tool with an undocumented identifier parameter and no annotations, the description omits identifier format, permissions, and sibling routing. It is under-specified for even this simple tool.

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 coverage is 0% for the single required change-id parameter, and the description adds nothing about its expected format. In Gerrit-style APIs the change identifier can be a numeric id, a triplet, or a Change-Id string, and that ambiguity is not resolved anywhere.

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 and resource: it retrieves the branches and tags that contain a given change, which is meaningfully narrower than the many sibling getChangesChangeId* tools. It stops short of differentiating itself explicitly from near-neighbours such as getProjectsProjectIdCommitsCommitIdIn, so an agent must infer the change-vs-commit 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 statement of when to use this tool, when not to, or which sibling to prefer when the goal is change metadata, reviewers, or commit inclusion. The agent is left to infer usage purely 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