Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidactions

getChangesChangeIdRevisionsRevisionIdActions

Retrieve the actions available for a specific revision of a Gerrit change to identify permitted review operations before performing them.

Instructions

Retrieves revision actions of the revision of a 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": "getChangesChangeIdRevisionsRevisionIdActions"
  }
}

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

C2.4/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 burden of behavioral disclosure and delivers none of it: no statement that this is a read-only fetch, no permission or access requirements, no mention of ordering, pagination, or empty results. The only behavioral hint is the verb 'Retrieves', which is minimal for a tool with zero annotation coverage.

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

Conciseness3/5

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

It is a single front-loaded sentence with nothing extraneous, which is good. However, the phrasing 'revision actions of the revision of a change' is awkwardly repetitive and could be tightened; brevity here comes at the cost of information rather than achieving both.

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?

An output schema exists, so return values need not be explained, and that reduces the burden. Still, for a tool taking two required identifiers with no schema documentation and no annotations, the description leaves the agent without parameter guidance or any behavioral context, which is inadequate.

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 parameters (change-id, revision-id) are undocumented in the schema. The description only weakly implies a containment hierarchy ('revision of a change'), giving no ID format, no example, and no indication of where either identifier comes from, 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.

Purpose3/5

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

The description has a verb ('Retrieves') and a resource ('revision actions of the revision of a change'), so the general shape is clear. But 'actions' is never defined, and the sentence gives no basis for distinguishing it from siblings such as getChangesChangeIdFlowsActions (actions at the change level) or getChangesChangeIdRevisionsRevisionId (the revision itself). It is barely above vague.

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 when-to-use or when-not-to-use guidance at all. The agent is not told how this differs from the change-level FlowsActions tool or from fetching the revision, so the choice among ~30 siblings is left entirely to inference.

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