Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidmessageschangemessageid

getChangesChangeIdMessagesChangeMessageId

Retrieve a specific ChangeMessageInfo entity from a Gerrit change by change ID and message ID to read a single change comment or message.

Instructions

As response a ChangeMessageInfo entity is returned.

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>",
      "change-message-id": "<change-message-id>"
    },
    "name": "getChangesChangeIdMessagesChangeMessageId"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
change-message-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, and the description discloses no operational behavior such as whether the call is read-only, how invalid or missing identifiers are handled, or whether permissions are required. Its sole return-type statement adds little behavioral value, especially because an output schema is present.

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

Conciseness2/5

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

The single sentence is short, but its brevity results from omitting nearly all invocation-relevant information. The awkward 'As response' wording and exclusive focus on the return type make it under-specified rather than effectively concise.

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

Completeness1/5

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

Although the output schema removes the need to explain return values, the description does not supply the missing purpose, parameter semantics, usage guidance, or behavior for an operation with two required identifiers. It is insufficient for confident tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both change-id and change-message-id are required strings with 0% schema description coverage, and the description explains neither identifier nor how to obtain it. It adds no parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names only the returned ChangeMessageInfo entity and never states a retrieval action or the relationship between the change and message. The tool name suggests a single-message lookup, but the description neither confirms that purpose nor distinguishes it from getChangesChangeIdMessages.

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, what prerequisites apply, or when to choose a sibling such as the change-messages collection operation. An agent must infer all selection criteria from the tool names.

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