Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Code Owners Getprojectsprojectidcodeownersprojectconfig

code_owners_getProjectsProjectIdCodeOwnersProjectConfig

Retrieves the code owner configuration for a specified Gerrit project, so you can inspect ownership rules and project-level settings.

Instructions

Gets the code owner project 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>"
    },
    "name": "code_owners_getProjectsProjectIdCodeOwnersProjectConfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/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 behavioral burden, and it adds essentially nothing beyond the word 'Gets'. It does not state the permission level needed, whether inheritance or defaults apply for a project-level config, or what happens when no config exists; only the output schema hints at the shape of the response.

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?

One short sentence with no filler, so it is concise, but conciseness here comes at the cost of under-specification rather than deliberate front-loading. There is no structure to speak of beyond a single clause.

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 needn't be explained, but for a tool with an opaque identifier parameter and a crowded family of code_owners_* siblings, the definition leaves the agent without the information needed to choose it confidently. The description should at minimum state the retrieval scope and any access requirement.

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% and the description never mentions the single parameter. The schema does name 'project-id' and mark it required, so an agent can infer it identifies the project, but the description contributes no meaning about accepted identifier formats or scoping.

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

Purpose2/5

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

The description almost verbatim restates the tool name: 'Gets the code owner project configuration' decodes to code_owners_getProjectsProjectIdCodeOwnersProjectConfig with no added specificity. It does convey read-only retrieval of a project-level code owner config, but there are many code_owners_* siblings and nothing here distinguishes this project-level config fetch from the branch-level or change-level variants.

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 at all. The description does not say when an agent should pick this project-scoped config call versus the branch-scoped siblings like code_owners_getProjectsProjectIdBranchesBranchIdCodeOwnersConfigFile, nor does it mention any prerequisites such as required permissions.

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