Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidsubmittype

getChangesChangeIdRevisionsRevisionIdSubmitType

Retrieves the submit type Gerrit will use to merge a specific change revision, clarifying whether the change will be merged, rebased, cherry-picked, or fast-forwarded.

Instructions

Gets the method the server will use to submit (merge) the change.

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

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.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does almost nothing with it. It omits that this is a read-only lookup, that the value is computed server-side from repository/branch configuration (so it may change without the revision changing), and whether any permissions are required to view it.

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 wasted words or filler. It is terse rather than bloated, though the terseness comes at the cost of the missing detail noted elsewhere.

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 small (two parameters, output schema present so return values need no explanation) and the description correctly conveys the core retrieval. However, with zero annotation coverage and zero schema coverage for required identifiers, the definition leaves an agent without enough detail to construct a valid call confidently.

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, so the description must compensate and it does not. It never explains the expected format of change-id (numeric id vs. project~branch~Change-Id triplet) or that revision-id selects which patchset's submit method is reported, leaving both parameters opaque.

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 concrete read operation: it returns 'the method the server will use to submit (merge) the change', which identifies both the verb (get) and the resource (submit method for a change/revision). It is reasonably distinct from siblings like getChangesChangeIdRevisionsRevisionIdMergeable, though it never uses the term 'submit type' that the tool name implies, so an agent must infer that equivalence.

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?

No when-to-use or when-not-to-use guidance is given. It does not say how this differs from getChangesChangeIdRevisionsRevisionIdMergeable or the project-level submit requirements tool, both of which are plausible alternatives for an agent asking 'can/how will this change be submitted'.

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