Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidcommentscommentid

getChangesChangeIdRevisionsRevisionIdCommentsCommentId

Retrieves a published comment from a specific revision using change, revision, and comment IDs, enabling you to inspect review feedback.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
change-idYes
comment-idYes
revision-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 does not state whether authentication or specific permissions are required, what happens when the comment is a draft or does not exist, or that the operation is read-only — only 'Retrieves' implies a safe read.

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

Conciseness3/5

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

A single short sentence with no wasted words and the key qualifier ('published') front-loaded. However, the brevity reflects under-specification rather than disciplined conciseness for a three-parameter tool.

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 with no annotations, 0% parameter documentation, and no usage guidance, the definition leaves too much for the agent to infer about a mutation-free but permission-sensitive fetch.

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% for all three required path parameters, so the description must compensate and does not. It adds no meaning about the change-id, revision-id, or comment-id beyond what their names and the tool name already convey.

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 names a specific verb and resource ('Retrieves a published comment of a revision'), and the word 'published' implicitly separates it from the draft-comment siblings. It does not explicitly name any sibling, but the resource is unambiguous.

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 single-comment fetch versus the sibling listing endpoints (e.g. the Comments collection or DraftsComment tools). The only implicit signal is 'published', which hints at excluding drafts but states no condition or alternative.

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