Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidportedcomments

getChangesChangeIdRevisionsRevisionIdPortedComments

Ports comments from other revisions to the requested revision of a Gerrit change, consolidating review feedback.

Instructions

Ports 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": "getChangesChangeIdRevisionsRevisionIdPortedComments"
  }
}

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.3/5.0
Behavior1/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, and it fails on the single most important question: whether this is a read or a mutation. It says nothing about permissions required, whether comments are moved or copied, whether the source revision is modified, or whether the operation is reversible. For a tool whose name and description disagree about read-vs-write semantics, this is a serious 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 padding and the action front-loaded. It is efficient, but the brevity is partly under-specification rather than disciplined concision.

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 values need not be described, but the definition still leaves the agent unable to determine whether invocation causes side effects, which is essential before calling. Relative to a two-parameter revision-scoped tool with zero annotation coverage and zero schema descriptions, one sentence is not enough.

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%, so both change-id and revision-id are undocumented in structured data. The description gestures at "other revisions" versus "the requested revision" but never explains that the two parameters identify the change and the target revision, nor what happens if the revision-id belongs to a different change.

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 description names a resource (comments of other revisions) and a target (the requested revision), so the subject matter is inferable. However, the verb "Ports" conflicts with the imperative GET framing of the tool name and of the sibling getChangesChangeIdRevisionsRevisionIdPortedDrafts, so an agent cannot tell whether this retrieves projected comments or actually performs a porting write. That ambiguity keeps it at minimum-viable rather than a clear verb+resource statement.

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 guidance, no exclusions, and no mention of the closely related siblings such as getChangesChangeIdRevisionsRevisionIdComments or the PortedDrafts variant. The agent is left to infer selection from the name alone.

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