Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Code Owners Getchangeschangeidcodeownersstatus

code_owners_getChangesChangeIdCodeOwnersStatus

Retrieve code owner statuses for files in a Gerrit change to verify required approvals per file.

Instructions

Gets the code owner statuses for the files in a 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>"
    },
    "name": "code_owners_getChangesChangeIdCodeOwnersStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo
change-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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 carries the full behavioral burden, yet it does not state that this is a read-only operation, whether results are paginated, or what the statuses represent (e.g., pending vs. approved vs. failed). Only the existence of an output schema mitigates the return-value gap.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes to the gaps noted in other dimensions rather than being a flaw of structure itself.

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 three-parameter endpoint with no annotations and zero schema description coverage, the description is too thin: pagination behavior, status semantics, and error/precondition cases are all unaddressed. The presence of an output schema excuses only the return-value explanation.

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% across three parameters. The description only hints at change-id via 'in a change'; the limit and start parameters are never mentioned, so their pagination role is left entirely undocumented in both schema and description.

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 gives a specific verb and resource: 'Gets the code owner statuses for the files in a change.' The phrase 'in a change' implicitly distinguishes it from the revision-scoped and project/branch-scoped code owner siblings, but the description never names or contrasts those alternatives explicitly.

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 change-level status endpoint rather than the revision-level or branch-config code owner siblings, nor any stated preconditions (e.g., that the change must exist or that code owners must be configured). The agent must infer selection from the tool name alone.

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