Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidcomments

getChangesChangeIdComments

Lists published comments across all revisions of a Gerrit change, grouped by file path, so you can review discussion history.

Instructions

Lists the published comments of all revisions of a change, 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>"
    },
    "name": "getChangesChangeIdComments"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
enable-contextNo
context-paddingNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose two real behaviors: only published comments are returned (drafts excluded, relevant given the getChangesChangeIdDrafts sibling) and results are grouped by file path. It says nothing about permissions, pagination, ordering, or how revisions are merged within a file group, which are the questions an agent would still have.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the scope and grouping behavior come first. Nothing in it is redundant, and there is no padding to trim.

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 shape need not be described. But a three-parameter tool with zero schema coverage and no annotations leaves the context parameters and the change-id format undefined, and gives no guidance on which sibling to choose for a single revision.

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 all three parameters are undocumented and the description compensates for none of them. In particular, "enable-context" and "context-padding" are non-obvious optional controls whose effect and interaction (padding presumably requires context enabled) are left entirely unexplained.

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 ("Lists the published comments") plus an explicit scope ("of all revisions of a change"), and the scope wording implicitly separates it from the per-revision sibling getChangesChangeIdRevisionsRevisionIdComments. It stops short of naming that sibling explicitly, so differentiation must be inferred from the schema rather than stated.

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 "of all revisions" implies this is the whole-change aggregate rather than the single-revision variant, which is usable guidance. However, there is no explicit when-to-use statement, no exclusion of the draft-viewing sibling, and no note on when the context parameters matter.

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