Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigserverexperimentsexperimentid

getConfigServerExperimentsExperimentId

Retrieve an experiment's details by name to inspect its configuration and status before using or troubleshooting it.

Instructions

Retrieves the details of the experiment with the given name.

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": {
      "experiment-id": "<experiment-id>"
    },
    "name": "getConfigServerExperimentsExperimentId"
  }
}

Input Schema

NameRequiredDescriptionDefault
experiment-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?

With no annotations, the description bears the full burden of behavioral disclosure. It implies a read but never states read-only semantics, does not say what happens when the id does not exist or when the caller lacks permission, and adds no context beyond the single retrieval sentence.

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?

A single sentence with no filler, which is good, but its brevity comes at the cost of specification rather than being genuinely tight. There is nothing to front-load because nothing else is said.

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 path parameter) and an output schema exists, so return values need not be described. Still, the name-vs-id ambiguity and the absence of any usage or error context leave gaps an agent would need to resolve by trial.

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 the description must compensate for the one parameter. Instead of clarifying format or source of the identifier, it calls it a 'name', which conflicts with the schema's 'experiment-id' naming and could lead an agent to pass the wrong value.

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 gives a clear verb and resource ('Retrieves the details of the experiment'), which is enough to understand the basic operation. However, it does not distinguish itself from the sibling list tool getConfigServerExperiments, and it refers to the lookup key as a 'name' while the tool is keyed by an experiment id, muddying the purpose slightly.

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 listing tool as the alternative for browsing experiments, and no prerequisites or failure conditions (e.g., unknown id). The agent must infer usage entirely from the 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