Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getplugins

getPlugins

Lists plugins installed on a Gerrit server, returning only enabled ones by default; set the all option to include disabled plugins.

Instructions

Lists the plugins installed on the Gerrit server. Only the enabled plugins are returned unless the all option is specified.

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

Input Schema

NameRequiredDescriptionDefault
rNo
allNo
limitNo
matchNo
startNo
prefixNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the default filtering behavior—only enabled plugins are returned unless 'all' is set—but does not state whether the operation is read-only, whether authentication is required, or how pagination and filtering behave.

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?

The description is two focused sentences with the main purpose stated first and the important default behavior immediately after. There is no redundant wording or filler.

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?

For a six-parameter listing endpoint with no annotations and no schema parameter descriptions, the definition covers only the basic purpose and the 'all' flag. Because an output schema exists, return values need not be explained, but the filtering, pagination, and matching parameters remain unexplained, leaving the tool under-specified for correct invocation.

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?

The input schema has six parameters and 0% description coverage, so the description must compensate. It explains only the 'all' parameter; the meanings of 'r', 'limit', 'match', 'start', and 'prefix' are left entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: it 'Lists the plugins installed on the Gerrit server.' It also clarifies the default scope by saying only enabled plugins are returned unless the 'all' option is specified, so an agent can distinguish this from plugin-detail or checks-related siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for listing installed plugins and explains the key 'all' switch for including disabled plugins. However, it does not name alternatives such as getPluginsPluginIdGerritStatus or checks_getPluginsChecksCheckers, nor does it state when this list endpoint should be preferred over those related tools.

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