Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Code Owners Getprojectsprojectidbranchesbranchidcodeownerscheck

code_owners_getProjectsProjectIdBranchesBranchIdCodeOwnersCheck

Checks whether a user owns code at a specified path in a branch, helping verify code ownership for review or submission.

Instructions

Checks the code ownership of a user 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>"
    },
    "name": "code_owners_getProjectsProjectIdBranchesBranchIdCodeOwnersCheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
userNo
emailNo
changeNo
branch-idYes
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full disclosure burden and does not meet it. It never states that this is a read-only verification, what permissions are required, how user/email/change are resolved, or what happens when only branch-id and project-id are given.

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?

A single short sentence with no filler, which is structurally clean and front-loaded. However, its brevity comes at the cost of under-specification rather than genuine tightness, so it earns only a middling score.

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?

For a six-parameter tool with zero schema documentation and no annotations, the description is far too thin. The presence of an output schema excuses it from describing return values, but the missing parameter semantics and usage context leave real 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% across six parameters, so the description must compensate and largely fails. It mentions only path, user, and branch, leaving email and especially 'change' unexplained, and it gives no hint about precedence between 'user' and 'email' or the format of the branch/project identifiers.

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 pairs a specific verb ('Checks') with a concrete resource ('code ownership of a user for a path in a branch'), which is materially more informative than the machine-mangled tool name. It does not, however, distinguish this check from neighboring code-owner endpoints such as ConfigPath, PathId, or BranchConf, so an agent still has to infer which 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 when-to-use guidance, no mention of prerequisites, and no reference to any alternative tool. The agent is left to guess whether this is the right call for validating a specific user against a path versus listing owners or suggesting reviewers.

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