Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisioniddraftsdraftcommenti

getChangesChangeIdRevisionsRevisionIdDraftsDraftCommentI

Retrieves a draft comment from a Gerrit revision when it belongs to the calling user, using change, revision, and draft comment IDs to fetch the specific review note.

Instructions

Retrieves a draft comment of a revision that belongs to the calling user.

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>",
      "draft-comment-id": "<draft-comment-id>"
    },
    "name": "getChangesChangeIdRevisionsRevisionIdDraftsDraftCommentI"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
revision-idYes
draft-comment-idYes

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?

No annotations are supplied, so the description carries the behavioral burden. It discloses the important authorization scoping (only the calling user's own draft), which is genuinely useful, but it says nothing about the failure mode for another user's draft, nor about the response shape — though an output schema exists and covers the latter.

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 padding. It is efficient, but its brevity is also the source of the missing parameter and failure-mode detail.

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 three-path-parameter read operation with an output schema covering the return value, the description is minimally adequate. The notable gap is identifier format and cross-user error behavior, which matter because the tool is explicitly scoped to the caller's own drafts.

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% and all three parameters are bare strings. The description implies the path hierarchy (change → revision → draft comment) but gives no format guidance, even though Gerrit change-ids can be numeric or project~branch~Change-Id triples. The agent is left to guess acceptable identifier formats.

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 (retrieves) and a specific resource (a draft comment of a revision), plus a scope qualifier (belongs to the calling user). That distinguishes it reasonably from the published-comment sibling getChangesChangeIdRevisionsRevisionIdCommentsCommentId and from the drafts list sibling, though it does not name either explicitly.

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?

Implicit guidance comes from the 'belongs to the calling user' clause, which tells the agent this only works on its own drafts. There is no explicit statement of when to prefer this over the drafts list or the published-comment getter, and no mention of what to do when the draft isn't the caller's.

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