Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidsubmittedtogether

getChangesChangeIdSubmittedTogether

Retrieves all changes submitted together when a specified Gerrit change is submitted, including the current change itself.

Instructions

Computes list of all changes which are submitted when Submit is called for this change, including the current change itself.

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

Input Schema

NameRequiredDescriptionDefault
oNo
change-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 behavioral burden. It clarifies the inclusion semantics of the result set, but never states that this is a read-only computation, whether it reflects the current state or a predicted future submission, or what happens for an abandoned/merged change — gaps that matter for a tool implying a write-triggering operation.

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 well-formed sentence that front-loads the core action and appends the key scope caveat. There is no filler, though it is terse to the point of omitting param explanations.

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?

An output schema exists, so return values need not be explained, and the computation's definition is stated. However, with zero annotation coverage and zero schema documentation for the 'o' parameter, the definition leaves an agent without enough information to supply that parameter correctly.

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 two parameters. The description never mentions 'change-id' (evident from the name, admittedly) and gives no meaning at all for the opaque 'o' array-of-strings parameter adjacent to it in the schema. With no schema documentation, the description should have compensated and does not.

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 ('Computes list of all changes which are submitted when Submit is called for this change') plus an important scope clarification ('including the current change itself'), which clearly separates it from single-change siblings like getChangesChangeId. It does not name any sibling, but the operation itself is unambiguous.

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?

The phrase 'when Submit is called for this change' implies the use case (pre-flight inspection of a submission), but there is no explicit statement of when to prefer this over sibling lookups or of any preconditions, such as whether the change must be in a submittable state.

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