Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidrobotcomments

getChangesChangeIdRevisionsRevisionIdRobotcomments

Retrieve robot comments for a specific revision in a Gerrit change to review automated feedback and address issues.

Instructions

Lists the robot comments of a 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": "getChangesChangeIdRevisionsRevisionIdRobotcomments"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
revision-idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 implies a read-only list operation but says nothing about pagination, ordering, permissions, empty results, or whether robot comments include resolved/outdated states.

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?

The description is a single front-loaded sentence with no filler. Its brevity is appropriate structurally, though it leaves important information unstated.

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?

The tool is a nested revision sub-resource with two required parameters, no annotations, and no output schema. A one-sentence description does not adequately cover parameter meaning, pagination/return behavior, or how this differs from the many sibling comment-related endpoints.

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 coverage is 0%, and both parameters are required but undocumented. The description implies that revision-id identifies the revision whose robot comments are listed, but it adds no format, hierarchy, or constraint details for change-id or revision-id.

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 states a specific verb and resource: it lists robot comments belonging to a revision. It distinguishes itself from general comment-listing tools by specifying 'robot comments,' though it does not explicitly contrast with the singular robot-comment sibling or regular comments.

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 explicit guidance on when to use this tool versus the sibling tools for regular comments, drafts, ported comments, or a single robot comment. Usage is only implied by the tool name and the phrase 'of a revision.'

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