Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidflowsflowid

getChangesChangeIdFlowsFlowId

Retrieves a specific flow on a Gerrit change using the change ID and flow ID.

Instructions

Gets a flow on 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>",
      "flow-id": "<flow-id>"
    },
    "name": "getChangesChangeIdFlowsFlowId"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow-idYes
change-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 supplied, so the description carries the full behavioral burden, yet it only implies a read via the verb "Gets." It says nothing about permissions on the change, what happens if the flow-id does not belong to the change-id, or error behavior.

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 no wasted words, but it is under-specified rather than concise — the brevity comes at the cost of meaning, not from trimming redundancy.

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 described, but for a nested resource fetch with two required, undocumented parameters and no annotations, the description leaves an agent without enough to call it 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%, so both required parameters (change-id, flow-id) are undocumented. The description's words "flow" and "change" loosely gesture at the two parameters but add no format, scoping, or validity information to 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?

"Gets a flow on the change" names a verb and a resource, but neither "flow" nor its relationship to the parent change is defined, and it does not distinguish itself from the sibling getChangesChangeIdFlows (which presumably lists flows). An agent can guess this fetches a single flow, but only by parsing the tool name.

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 the sibling list tool, and no stated prerequisites such as needing a valid change-id before a flow-id. The only signal is the implicit singular/plural distinction in the names.

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