Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigserverexperiments

getConfigServerExperiments

Lists experiments available in the system and optionally filters to enabled ones, helping you inspect configuration capabilities.

Instructions

Lists the experiments that are available in the system.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getConfigServerExperiments"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabled-onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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 supplied, so the description carries the full burden, yet it discloses almost nothing: no statement about whether the result is filtered by default, whether only enabled/active experiments appear, whether authentication or admin scope is required, or how large the list can get. Only the bare fact that a list is returned is conveyed.

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 short sentence that is front-loaded with the verb and resource, with no filler. Its brevity is achieved honestly rather than through padding, though the space saved is not used to add any useful detail.

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?

Because an output schema exists, return values need no explanation, but the definition still leaves critical gaps: the filter parameter is undocumented and there is no behavioral or scoping context for a no-annotation tool. For a collection endpoint with a meaningful filter, this is under-specified.

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 the single optional parameter ("enabled-only") is never mentioned in the description. That parameter materially changes the result set, so the omission leaves the caller guessing at semantics such as its default value and what happens when it is omitted.

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 experiments") with the scope "available in the system", which is clear enough to act on. It does not differentiate from the sibling getConfigServerExperimentsExperimentId, so the agent must infer that this is the collection-level listing versus a single-experiment detail call.

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?

No when-to-use guidance, no when-not-to-use, and no mention of the obvious alternative (fetching a single experiment by ID). The agent is left to infer the routing from tool names alone.

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