Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidporteddrafts

getChangesChangeIdRevisionsRevisionIdPortedDrafts

Ports draft comments from other revisions to the requested revision of a Gerrit change, aligning review feedback with the target revision.

Instructions

Ports draft comments of other revisions to the requested revision.

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

Input Schema

NameRequiredDescriptionDefault
change-idYes
revision-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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. It implies a state-changing operation but says nothing about whether existing drafts on the target revision are overwritten, what permissions or authorship rules apply, or whether the action is reversible. With an output schema present, return-value detail is not required, but mutation semantics are a real gap.

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 with no filler and the operation front-loaded. It is efficient, though its brevity is partly under-specification rather than disciplined compression.

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 mutating tool with no annotations and zero schema coverage on both required parameters, one sentence cannot be sufficient. The output schema excuses it from describing responses, but an agent still cannot tell what this modifies, under what conditions, or how it differs from adjacent tools.

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

Parameters3/5

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

Schema description coverage is 0%, so the description should compensate for two undocumented parameters. It references "other revisions" and "the requested revision" but never explains which one is the source versus the target of change-id/revision-id, leaving the mapping implicit; the parameter names are conventional enough that this is a modest rather than fatal gap.

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?

The verb "Ports" with the object "draft comments of other revisions" does identify an operation and a target resource, so the intent is roughly graspable. But "port" is domain jargon that is never unpacked, and the description does not distinguish this tool from the near-identical sibling getChangesChangeIdRevisionsRevisionIdPortedComments.

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 this operation is appropriate, what preconditions must hold (e.g., must the source revision have drafts, must the caller be the draft author), or when the sibling PortedComments should be used instead. The agent is left to infer everything from the title.

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