Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Checks Getchangeschangeidrevisionsrevisionidchecks

checks_getChangesChangeIdRevisionsRevisionIdChecks

Retrieves all checks for a specified change revision, enabling you to review check results for that exact revision.

Instructions

Retrieves all checks for a given revision and change.

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>"
    },
    "name": "checks_getChangesChangeIdRevisionsRevisionIdChecks"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
revision-idYes

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 should state the behavioral details itself. It says nothing about authentication and permission requirements, pagination, ordering, or what is returned when a revision has no checks; all of these are left implicit in a read operation.

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?

The description is a single front-loaded sentence with no filler, so it is easy to scan. Its brevity is efficient, but it also leaves the definition under-specified, which costs it a point.

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?

With no annotations, no output schema, and zero schema description coverage, the description carries the full burden of explaining the tool, and one sentence is not enough. An agent still cannot tell how to format the change id or what the response looks like.

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 coverage is 0%, so the description must explain the two required parameters. It only restates their names as 'change-id' and 'revision-id' and gives no format hints, such as the project~branch~changeId triple or a numeric revision id versus 'current'.

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 specific verb and resource: 'Retrieves all checks for a given revision and change.' That contrasts implicitly with the sibling tool that fetches a single check by check-id, so an agent can tell the collection endpoint from the item endpoint.

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 guidance on when to use this tool instead of the per-check sibling or the plugin checkers tool, and no preconditions such as permissions or whether the change or revision must exist. The agent must infer the usage context 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