Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Code Owners Getprojectsprojectidbranchesbranchidcodeownerspathid

code_owners_getProjectsProjectIdBranchesBranchIdCodeOwnersPathId

Lists code owner accounts for a file or folder in a Gerrit branch to identify reviewers or approvers.

Instructions

Lists the accounts that are code owners of a file or folder in a branch.

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": {
      "project-id": "<project-id>",
      "branch-id": "<branch-id>",
      "path-id": "<path-id>"
    },
    "name": "code_owners_getProjectsProjectIdBranchesBranchIdCodeOwnersPathId"
  }
}

Input Schema

NameRequiredDescriptionDefault
ONo
oNo
seedNo
debugNo
limitNo
path-idYes
revisionNo
branch-idYes
project-idYes
resolve-all-usersNo
highest-score-onlyNo

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?

With no annotations, the description carries the entire behavioral burden, and it discloses almost nothing: no read-only confirmation (implied only by 'Lists'), no permission or access requirements, no pagination behavior despite a 'limit' parameter, and no explanation of how unresolvable or group owners are reported. It reveals only the existence of a lookup, not how the lookup behaves.

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?

It is a single front-loaded sentence with no filler, which is structurally clean. However, the terseness is under-specification rather than economy: it saves words that the agent actually needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An 11-parameter tool with 0% schema coverage, no annotations, and no output schema is described in one clause. Nothing explains the parameter semantics, behavioral constraints, or result shape, so the definition is not sufficient to call the tool correctly.

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% across 11 parameters, and the description explains none of them. Ambiguous fields such as 'O', 'o', 'seed', 'debug', 'resolve-all-users', 'highest-score-only', 'revision', and 'limit' have no meaning supplied anywhere, so the agent is guessing on nearly every input.

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: 'Lists the accounts that are code owners of a file or folder in a branch.' It is clear what the tool returns and its scoping (branch-level, path-level). It stops short of distinguishing itself from siblings such as code_owners_getChangesChangeIdRevisionsRevisionIdCodeOwnersPathId or getProjectsProjectIdBranchesBranchIdSuggestReviewers, so an agent cannot tell from the text alone which sibling applies when.

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 prerequisites, and no mention of alternative tools. The purpose sentence implies the use case (find owners for a path), but the agent must infer both the trigger condition and the branch/changes distinction on its own.

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