Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Code Owners Getprojectsprojectidbranchesbranchidcodeownersconfigfile

code_owners_getProjectsProjectIdBranchesBranchIdCodeOwnersConfigFile

Lists code owner config files in a branch, with optional path and email filters, to help you locate ownership rules for a project branch.

Instructions

Lists the code owner config files 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>"
    },
    "name": "code_owners_getProjectsProjectIdBranchesBranchIdCodeOwnersConfigFile"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
emailNo
branch-idYes
project-idYes
include-non-parsable-filesNo

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?

No annotations are supplied, so the description carries the full behavioral burden, yet it only restates the listing action. It says nothing about whether path/email act as filters, whether results are paginated, or what include-non-parsable-files changes about the output.

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?

It is a single front-loaded sentence with no filler. It is concise to a fault: brevity here reflects under-specification rather than tight writing.

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?

An output schema exists so return values need not be explained, but for a five-parameter tool with no annotations and 0% schema coverage, the description omits filtering semantics and behavior of the optional flags. It is not complete enough for an agent to call this correctly without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, but the description's mention of a branch does map onto project-id and branch-id. The three optional parameters (path, email, include-non-parsable-files) receive no meaning beyond their names, which is a real gap for a 5-parameter tool.

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 names a specific verb and resource: 'Lists the code owner config files in a branch.' An agent can tell this is a listing operation scoped to a branch, but it does not distinguish itself from close siblings such as code_owners_getProjectsProjectIdBranchesBranchIdCodeOwnersConfigPath, which presumably fetches a single config file.

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 listing versus fetching a specific config path or the project-level config, and no mention of prerequisites or exclusions. The agent must infer selection from the 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