Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrobotcomments

getChangesChangeIdRobotcomments

Retrieve all robot comments across every revision of a Gerrit change to review automated feedback and address issues.

Instructions

Lists the robot comments of all revisions of the change.

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

Input Schema

NameRequiredDescriptionDefault
change-idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations, no output schema, so the description carries the full behavioral burden. It discloses the "all revisions" scope, which is genuine value, but says nothing about pagination, ordering, permissions, or what a robot comment record contains.

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?

One short front-loaded sentence with no filler, though readability suffers from the missing spacing in the name-derived phrasing. Nothing is wasted, but there is little structure to speak of.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list with one parameter, the description covers the essential scope. It leaves the lone parameter and the return shape entirely to inference, which is a meaningful gap given the empty schema and absent annotations.

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 the single change-id parameter is undocumented in the schema, so the description would need to compensate. It only implies the parameter via "the change" and adds no format, source, or constraint details.

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 ("Lists") and resource ("robot comments of all revisions of the change"), which is enough to know what data comes back. It does not, however, distinguish itself from the sibling getChangesChangeIdRevisionsRevisionIdRobotcomments, which appears to narrow the same resource to a single revision.

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?

No when-to-use or when-not-to-use guidance is given; the only hint at selection is the phrase "all revisions." An agent must infer from the sibling name that the revision-scoped variant exists and when to prefer it.

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