Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Code Owners Getprojectsprojectidbranchesbranchidcodeownersconfigpath

code_owners_getProjectsProjectIdBranchesBranchIdCodeOwnersConfigPath

Retrieve the code owner configuration for a specific path in a project branch to understand ownership rules and required reviewers.

Instructions

Gets a code owner config for a path 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_getProjectsProjectIdBranchesBranchIdCodeOwnersConfigPath"
  }
}

Input Schema

NameRequiredDescriptionDefault
path-idYes
branch-idYes
project-idYes

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 supplied, so the description carries the full disclosure burden for a read tool, yet it says nothing about permission requirements, what happens when no config exists for the path, or the shape of the returned data. One sentence cannot cover the behavioral profile of a three-parameter lookup.

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 its brevity here reflects under-specification rather than disciplined economy given the 0% schema coverage it must offset.

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?

With no annotations, no output schema, and zero parameter documentation, the definition leaves too much for the agent to infer. For a lookup tool in a crowded family of near-identically named siblings, it should at minimum clarify parameter meaning and how it differs from the ConfigFile and BranchConf variants.

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 all three parameters (project-id, branch-id, path-id) are undocumented. The description only loosely hints at path and branch and never explains identifier formats, whether path-id is a numeric ID or a file path, or what project-id expects — a significant gap that the description does not compensate for.

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 names a verb ("Gets") and a resource ("code owner config") scoped to "a path in a branch," so the general intent is graspable. However, it does not distinguish this from close siblings such as the PathId, ConfigFile, and BranchConf variants, leaving the agent to guess which config variant it needs.

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 tool versus the many sibling code-owner tools, no prerequisites, and no exclusions. The agent must infer selection entirely from the tool name.

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