Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Checks Getchangeschangeidrevisionsrevisionidcheckscheckid

checks_getChangesChangeIdRevisionsRevisionIdChecksCheckId

Retrieves details for a specific check on a Gerrit change revision using the change ID, revision ID, and check ID.

Instructions

Retrieves a check.

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>",
      "revision-id": "<revision-id>",
      "check-id": "<check-id>"
    },
    "name": "checks_getChangesChangeIdRevisionsRevisionIdChecksCheckId"
  }
}

Input Schema

NameRequiredDescriptionDefault
ONo
oNo
check-idYes
change-idYes
revision-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?

No annotations are provided, so the description carries the full behavioral burden. The word 'Retrieves' implies a read-only operation, but there is no detail about permissions, error behavior, or what the returned check contains. The output schema covers the return shape, but the description adds virtually no behavioral context beyond the basic read implication.

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 description is a single short sentence with no wasted words, so it is concise and front-loaded. However, it is under-specified rather than appropriately sized for a tool with five parameters and no annotation coverage.

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?

An output schema exists, so return values need not be explained, but the input side is completely opaque. With three required IDs and two undocumented parameters, the description should explain at least what the check-id, change-id, and revision-id identify. As written, it is far too sparse for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the tool has five parameters, including three required IDs and cryptic 'O'/'o' parameters. The description says nothing about any parameter, so it does not compensate for the undocumented schema at all.

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 clear verb and resource: 'Retrieves a check.' An agent can tell this is a read operation for a check entity, but the description does not differentiate it from the sibling collection tool that also deals with checks, nor does it mention the change/revision scoping that the tool name implies.

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?

The description gives no guidance about when to use this tool versus the sibling checks listing tool or other revision-related tools. It also omits prerequisites such as required IDs or permissions, leaving the agent to infer usage solely from the name and schema.

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