Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidflowsactions

getChangesChangeIdFlowsActions

Lists the flow actions configured for a given change in Gerrit, so you can inspect available actions before triggering them.

Instructions

Lists the flows actions that are configured for the given 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>"
    },
    "name": "getChangesChangeIdFlowsActions"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-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 disclosure burden, yet it says nothing about read-only semantics, permissions, pagination, or result size. "Lists" weakly implies a read, but that is an inference rather than a stated trait.

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 efficient sentence with the resource and scope front-loaded and no filler. Minor deduction because "flows actions" is ambiguous phrasing that could have been made precise at no extra length.

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 simple (one required parameter) and an output schema covers return values, so the description is not obligated to explain results. Still, with no annotations and zero parameter documentation, the definition leaves the agent guessing about read-only behavior and which sibling listing this represents.

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

Parameters3/5

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

Schema coverage is 0%, so the sole change-id parameter is documented nowhere else. The phrases "the given change" and "configured for" tie the parameter to a change entity, which adds a little meaning, but no format, ID type, or example is supplied.

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 names a verb ("Lists") and a resource ("flows actions... for the given change"), so the basic operation is identifiable. However, "flows actions" is an unclear compound, and the description does nothing to distinguish this from sibling tools like getChangesChangeIdFlows, getChangesChangeIdFlowsFlowId, or getChangesChangeIdRevisionsRevisionIdActions, so an agent cannot confidently choose among them.

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 guidance, no prerequisites, and no mention of alternatives. The agent is left to infer that this is the change-level flow-actions listing rather than the flow-scoped or revision-scoped variant purely from the tool 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