Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisioniddrafts

getChangesChangeIdRevisionsRevisionIdDrafts

Lists the calling user's draft comments on a Gerrit revision, grouped by file path.

Instructions

Lists the draft comments of the calling user on a revision, grouped by file path.

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

Input Schema

NameRequiredDescriptionDefault
change-idYes
revision-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does usefully disclose two traits beyond the name: results are limited to the caller's own drafts and are grouped by file path, and 'Lists' implies a read-only operation. It says nothing about permissions required, pagination, or whether other users' drafts are visible.

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; the scope qualifier ('of the calling user') and the grouping behavior come before any subordinate detail. It is efficient, though its brevity reflects under-specification rather than tight editing.

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?

The tool is structurally simple (two required path-style identifiers) and an output schema exists, so return-value shape needn't be described. Still, for a no-annotation endpoint the definition omits permissions, pagination, and parameter meaning, leaving it only minimally sufficient.

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 both required parameters (change-id, revision-id) are bare strings. The description mentions 'a revision' but never explains change-id, how the two identifiers relate, or what formats they take, so it does not compensate for the coverage gap.

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 ('Lists') and a precisely scoped resource: draft comments belonging to the calling user on a revision, grouped by file path. The 'calling user' and 'draft' qualifiers implicitly separate it from the published-comments and ported-drafts siblings, though no sibling is named explicitly.

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 when-to-use or when-not-to-use guidance and no alternative tool is named, even though the sibling set contains closely related comment endpoints (comments, ported drafts, single draft). The agent must infer that this is the right choice for its own unpublished drafts.

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