Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Checks Getpluginscheckscheckerscheckerid

checks_getPluginsChecksCheckersCheckerId

Retrieves a specific Gerrit checks checker by its checker ID, enabling you to inspect plugin-based checker configuration and details for review validation workflows.

Instructions

Retrieves a checker.

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": {
      "checker-id": "<checker-id>"
    },
    "name": "checks_getPluginsChecksCheckersCheckerId"
  }
}

Input Schema

NameRequiredDescriptionDefault
checker-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 carries the full burden and discloses almost nothing beyond the word "Retrieves." It does not state that the operation is read-only, what happens for an unknown checker-id, or any permission/plugin-enablement requirement.

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?

The single sentence is front-loaded and free of padding, but its brevity reflects under-specification rather than efficiency. There is no wasted wording, but also no structure beyond a bare statement.

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?

The presence of an output schema excuses it from describing return values, but for a parameterized fetch with no annotations and an undocumented id parameter, the description leaves key calling information missing. It is not complete enough to invoke confidently without inspecting the schema and guessing semantics.

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 single parameter checker-id has 0% schema description coverage, and the description adds no meaning about its format, where it comes from, or whether it is plugin-qualified. With low coverage, the description should have compensated and does not.

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?

"Retrieves a checker" names a verb and resource, so the basic operation is clear, but it does not explain what a checker is nor distinguish it from the sibling list endpoint checks_getPluginsChecksCheckers or the change-scoped checks endpoints. An agent can guess this is a single-object fetch, but only from the id parameter 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 statement of prerequisites (e.g., that the checker plugin must be enabled), and no mention of when to use the list sibling instead. The only usage signal is implicit in the required checker-id.

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