Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Code Owners Getchangeschangeidrevisionsrevisionidcodeownerspathid

code_owners_getChangesChangeIdRevisionsRevisionIdCodeOwnersPathId

Suggests accounts that are code owners of a file in a specific change revision, helping you identify the right reviewers to add.

Instructions

Suggests accounts that are code owners of a file in a change revision.

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>",
      "path-id": "<path-id>"
    },
    "name": "code_owners_getChangesChangeIdRevisionsRevisionIdCodeOwnersPathId"
  }
}

Input Schema

NameRequiredDescriptionDefault
ONo
oNo
seedNo
debugNo
limitNo
path-idYes
change-idYes
revision-idYes
resolve-all-usersNo
highest-score-onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 disclosure burden. The word 'suggests' hints at heuristic scoring rather than an exhaustive list, which is genuinely useful, but nothing is said about permissions, pagination, or what the debug/seed/limit controls do. For a 10-parameter tool with zero annotation coverage this leaves major behavioral gaps.

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 filler, but it is under-specified for a tool of this complexity rather than genuinely concise. Nothing in the sentence is wasted, yet a great deal is left unsaid.

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?

Given 10 parameters, no annotations, and no output schema, the definition is far too thin. It does not indicate the shape of the returned owner suggestions, how scoring or limits behave, or what the randomizing 'seed' parameter changes.

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 10 parameters, including cryptic names like 'O', 'o', 'seed', 'debug', 'resolve-all-users', and 'highest-score-only'. The description only loosely maps to change-id/revision-id/path-id and explains none of the behavioral modifiers, so it fails to compensate for the schema gap.

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: it 'suggests accounts that are code owners of a file in a change revision.' That is clearly distinct from a generic lookup and implies ranked/suggested results. It does not, however, distinguish itself from the close sibling code_owners_getChangesChangeIdRevisionsRevisionIdOwnedPaths.

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 mention of prerequisites, and no named alternative. An agent must infer from the name alone that this returns owner suggestions while OwnedPaths returns paths with owners.

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