Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidpurerevert

getChangesChangeIdPureRevert

Checks whether a Gerrit change is a pure revert of its referenced change or a specified commit, so you can verify revert correctness before review.

Instructions

Check if the given change is a pure revert of the change it references in revertOf. Optionally, the query parameter o can be passed in to specify a commit (SHA-1 in 40 digit hex representation) to check against. It takes precedence over revertOf. If the change has no reference in revertOf, the parameter is mandatory.

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>"
    },
    "name": "getChangesChangeIdPureRevert"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
claimed-originalNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavioral rules: the optional commit parameter takes precedence over revertOf, and that parameter becomes mandatory when revertOf is absent. It does not state that this is a non-mutating check, nor how it behaves on a missing/inaccessible change, so coverage is partial rather than complete.

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?

Four short sentences, front-loaded with the core purpose and followed by the conditional rules. Nothing is padding, though the switch from 'o' to the concept of a commit value mid-paragraph makes the middle slightly harder to follow than necessary.

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

Completeness4/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, and for a two-parameter read-style check the description covers the essential call semantics including the conditional requirement. The remaining gap is the parameter-name inconsistency and the absence of any note on error or not-found behavior.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it largely does: it explains that the optional value is a commit SHA-1 in 40-digit hex, that it overrides revertOf, and that it is required when revertOf is empty. The one flaw is a naming mismatch — the description calls it the query parameter 'o' while the schema property is 'claimed-original', which could confuse an agent mapping the value to the field.

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 opens with a specific verb and outcome: 'Check if the given change is a pure revert of the change it references in revertOf.' An agent immediately knows this is a boolean-style validation check on a change, not a mutation. It does not differentiate itself from the many sibling change sub-resource endpoints, but the purpose itself 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies conditional guidance ('If the change has no reference in revertOf, the parameter is mandatory') and a precedence rule, which helps an agent decide how to call it. However, it never states when to prefer this over related change-inspection endpoints or what the tool is for in a workflow, so usage is only implied.

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