Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Code Owners Getprojectsprojectidbranchesbranchidcodeownersbranchconf

code_owners_getProjectsProjectIdBranchesBranchIdCodeOwnersBranchConf

Retrieves the code owner configuration for a specific project branch, so you can verify ownership rules and branch-level settings before review or change submission.

Instructions

Gets the code owner branch configuration.

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_getProjectsProjectIdBranchesBranchIdCodeOwnersBranchConf"
  }
}

Input Schema

NameRequiredDescriptionDefault
branch-idYes
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are provided, so the description carries the full burden, yet it only implies a read via the verb "Gets". It says nothing about permissions, whether an unconfigured branch yields an error or empty result, or any rate-limit or side-effect behavior. The only positive signal is the implicit read-only framing.

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 definition is a single short sentence with no filler and is trivially front-loaded. But the brevity reflects under-specification rather than discipline; there is no structure telling the agent anything actionable.

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-value explanation is not required. Still, for a tool with two required identifiers, zero schema coverage, and no annotations, the description omits the parameters' meaning and any behavioral context, leaving meaningful gaps.

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%, so the two required string parameters (project-id, branch-id) are undocumented in both schema and description. The description adds no meaning about identifier formats, accepted values, or what a missing/unknown value yields, which it needs to do at this coverage level.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and object ("Gets the code owner branch configuration"), which is clearer than a tautology. However, it does not differentiate from close siblings such as code_owners_...CodeOwnersConfigFile, ...ConfigPath, ...Check, or ...PathId, all of which operate on the same project/branch scope. An agent cannot confidently pick this tool over those without opening schemas.

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 alternatives, and no prerequisites or exclusions. The sentence only implies usage through the resource name, leaving the agent to infer the selection criteria entirely.

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