Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidcomments

getChangesChangeIdRevisionsRevisionIdComments

Retrieve published comments for a specific Gerrit revision, grouped by file path, to review feedback on changed files.

Instructions

Lists the published comments of a revision, grouped by file path.

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

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.9/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 discloses the grouping behavior of the response, but says nothing about the read-only nature being confirmed, permission or visibility requirements for seeing published comments, pagination of potentially large comment lists, or whether unresolved and resolved comments are both included.

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 sentence with no filler, and the function and scope are front-loaded. It is efficient, though the brevity comes partly from omitting information that would have been useful.

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 explained. But for a two-argument endpoint sitting in a dense family of comment-related siblings, the definition gives no disambiguation from the drafts or ported-comments variants and no parameter detail, leaving the agent to guess at invocation specifics.

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 parameters are bare strings named only by convention. The description never mentions change-id or revision-id, nor whether either accepts a numeric ID, a hash, or a branch name for the revision. The gap the schema leaves is not filled.

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 and resource: "Lists the published comments of a revision." The qualifier "published" is doing real work, implicitly separating this from sibling tools for drafts, ported comments, and robot comments, and "grouped by file path" describes the shape of the result. It stops short of naming the sibling it displaces, so it is clear but not fully differentiated.

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?

There is no explicit when-to-use or when-not-to-use guidance. The word "published" is the only signal that this is not the drafts or ported-comments endpoint, and that inference is left entirely to the reader. Adequate but reliant on implication.

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