Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidisflowsenabled

getChangesChangeIdIsFlowsEnabled

Determines whether flows are enabled for a Gerrit change using its change ID.

Instructions

Returns whether flows are enabled for this 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": "getChangesChangeIdIsFlowsEnabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/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. 'Returns' establishes this as a read operation and the boolean nature of the result, but nothing is said about permission requirements, behavior for a non-existent or inaccessible change-id, or error signaling. That is an adequate but thin behavioral profile for a simple read.

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

Conciseness5/5

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

A single front-loaded sentence with no filler, no redundancy, and no ambiguity about what is being returned. Nothing could be trimmed without losing meaning.

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 the returned value needn't be explained, and the operation is simple enough that a one-liner is close to sufficient. However, with no annotations and no parameter documentation, an agent still lacks guidance on when to call this versus the adjacent flows tools and on failure behavior.

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 the single required change-id parameter. The phrase 'for this change' only weakly confirms that change-id identifies the target change; there is no mention of ID format, source, or validity constraints to compensate for the undocumented schema.

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 specific verb and resource ('Returns whether flows are enabled') for a named entity ('this change'), which is clear. It implicitly contrasts with the sibling getChangesChangeIdFlows (which lists flows) by returning a boolean flag, but it never says so explicitly, leaving full sibling differentiation to inference.

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 guidance on when to use this boolean check versus getChangesChangeIdFlows or the other flows-related endpoints, and no stated prerequisites or exclusions. The agent must infer usage purely from the name and the single sentence.

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