Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidflows

getChangesChangeIdFlows

Lists the flows of a Gerrit change that are visible to the caller, so you can inspect available workflow states and permission-scoped actions for that change.

Instructions

Lists the flows of a change that are visible to the caller.

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

Input Schema

NameRequiredDescriptionDefault
change-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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 it does disclose one meaningful trait: results are filtered to what the caller can see, implying permission-based scoping rather than an exhaustive list. It says nothing about pagination, ordering, or what an empty result means, which leaves real gaps for an unannotated read tool.

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 filler or redundant restatement of the title. It is efficient, though the terseness leaves little room for the guidance the tool actually lacks.

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?

An output schema exists, so return values need no explanation, and there is only one self-evident parameter. However, with zero annotations the description should still cover access requirements, result set behavior, and relationship to the flow-detail and actions siblings; those are absent.

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 description coverage is 0%, so the description must compensate; 'of a change' at least maps change-id to the change whose flows are returned. It adds no format, sourcing, or validation detail (e.g. where a change-id comes from or whether a numeric ID is accepted), so it only partially covers the single parameter.

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?

States a specific verb and resource ('Lists the flows of a change') plus a scope qualifier ('visible to the caller'), which separates it from the singular sibling getChangesChangeIdFlowsFlowId and from getChangesChangeIdFlowsActions. It never explicitly names those siblings, but the read-collection semantics are unambiguous.

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 mention of when to prefer the per-flow or actions siblings, and no stated preconditions such as required permissions on the change. The agent must infer the usage context entirely from the tool name and the one required parameter.

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