Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisioniddescription

getChangesChangeIdRevisionsRevisionIdDescription

Retrieves the description text for a specific patch set revision in Gerrit using a change ID and revision ID, helping you inspect commit message details.

Instructions

Retrieves the description of a patch set.

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

Input Schema

NameRequiredDescriptionDefault
change-idYes
revision-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Retrieves' implies a read-only operation, but it says nothing about permissions, whether the description can be null for certain patch sets, or any other behavioral trait; the presence of an output schema offsets only the return-value aspect.

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 short, front-loaded sentence with no filler. It is efficient, though the brevity stems partly from under-specification rather than tightness.

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 two-parameter tool with zero annotation coverage and zero schema descriptions, the description is too thin: it leaves identifier formats and behavioral expectations unaddressed. The output schema reduces the need to describe return values, but the input side remains undocumented.

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 two required parameters, and the description adds nothing about them. Notably, 'change-id' in this API is a compound identifier whose format is non-obvious, and the description does not clarify it or how revision-id is expressed.

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 ('Retrieves') and resource ('the description of a patch set'), which is distinguishable from siblings that fetch files, comments, checks, or mergeability. It is clear but does not explicitly contrast itself with any alternative endpoint.

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 siblings such as the parent revision endpoint or other revision sub-resources, nor any prerequisite or exclusion. Usage is only inferable from the resource name.

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