Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchanges

getChanges

Query Gerrit changes visible to you using repeatable query parameters, then page results with limit/start and request extra fields for detailed review.

Instructions

Queries changes visible to the caller. The query is given by the repeatable query parameter; use limit/start to page and o to request extra fields.

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

Input Schema

NameRequiredDescriptionDefault
ONo
oNo
limitNo
queryNo
startNo
no-limitNo
skip-visibilityNo
allow-incomplete-resultsNo

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

There are no annotations, so the description must carry the full behavioral burden. It implies a read-only query and mentions visibility and pagination, but it does not explain the effects of no-limit, skip-visibility, or allow-incomplete-results.

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 compact and front-loads the core purpose. Its sentences are efficient, though the mention of o is ambiguous without additional context.

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 tool has eight parameters, zero schema description coverage, and no annotations. Although an output schema exists, the description does not cover most input parameters or explain important behavioral flags.

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%, and the description only mentions query, limit, start, and o. It leaves O, no-limit, skip-visibility, and allow-incomplete-results undocumented, and it does not clarify query syntax or what extra fields o returns.

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: it queries changes visible to the caller. It does not explicitly distinguish this list/search tool from the many getChangesChangeId sibling tools.

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?

It gives some usage guidance by mentioning limit/start for paging and o for requesting extra fields. However, it does not explain when to use this tool versus getChangesChangeId or any other sibling.

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