Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidrobotcommentsrobotc

getChangesChangeIdRevisionsRevisionIdRobotcommentsRobotC

Retrieves a specific robot comment from a Gerrit change revision using the change, revision, and robot-comment IDs.

Instructions

Retrieves a robot comment 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>",
      "robot-comment-id": "<robot-comment-id>"
    },
    "name": "getChangesChangeIdRevisionsRevisionIdRobotcommentsRobotC"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
revision-idYes
robot-comment-idYes

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?

With no annotations supplied, the description carries the full behavioral burden. 'Retrieves' implies a read-only operation, but permissions, authentication requirements, error behavior for a nonexistent robot-comment-id, and the shape of the returned comment are all unstated.

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, front-loaded sentence with no filler. It is appropriately sized for a simple read endpoint, though its brevity reflects under-specification rather than disciplined editing.

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 tool requiring three identifiers and exposing no output schema or annotations, the description should explain at least what is returned and how the IDs relate. It says nothing an agent could not infer from the parameter names alone.

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 must compensate, and it only partially does: 'of a revision' hints that revision-id and change-id scope the lookup. It adds nothing about identifier formats (e.g., numeric vs hash) or how robot-comment-id is obtained, so the three required parameters remain largely 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: 'Retrieves a robot comment of a revision.' An agent can distinguish it from the plural sibling getChangesChangeIdRevisionsRevisionIdRobotcomments by the singular 'a robot comment', although the description never states that contrast explicitly. It is clear but lacks explicit sibling differentiation.

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 to use this tool versus the plural robot-comments list endpoint or the general comments endpoints. No prerequisites, no exclusions, and no mention of what a 'robot comment' is or where robot-comment-id comes from are provided.

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