Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Code Owners Getchangeschangeidrevisionsrevisionidownedpaths

code_owners_getChangesChangeIdRevisionsRevisionIdOwnedPaths

Lists revision files owned by a specified user to identify code ownership for a Gerrit change revision.

Instructions

Lists the files of the revision that are owned by the specified user (see user request parameter below).

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": {
      "change-id": "<change-id>",
      "revision-id": "<revision-id>"
    },
    "name": "code_owners_getChangesChangeIdRevisionsRevisionIdOwnedPaths"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo
limitNo
startNo
change-idYes
revision-idYes
check_reviewersNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 burden. It implies a read-only listing scoped to a user, but says nothing about pagination behavior, what happens when user is omitted, or what check_reviewers changes. It also doesn't clarify whether unowned files or an empty result are returned.

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?

A single compact sentence with the core scope front-loaded and no filler. The trailing parenthetical '(see user request parameter below)' is slightly awkward since the schema is not literally 'below' in a tool call, but it costs little.

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 with no annotations and 0% parameter documentation the description should carry more. It leaves the agent guessing about three undocumented parameters and the tool's relationship to adjacent code-owners endpoints.

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 6 parameters, and the description only touches on 'user' (and indirectly revision). The meaning of limit, start, and check_reviewers is left entirely undefined in both the schema and the description, which is a substantial gap for a 6-param 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?

States a specific verb (Lists) and a specific resource (files of the revision owned by the specified user), so an agent can tell it apart from sibling tools like code_owners_getChangesChangeIdRevisionsRevisionIdCodeOwnersPathId. It stops short of explicitly naming which sibling to prefer, which keeps it from a 5.

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 over the many sibling listing tools (e.g. getChangesChangeIdRevisionsRevisionIdFiles, checks_*), nor any prerequisites or exclusions. The only hint at usage is the parenthetical pointing to the user parameter, which explains nothing about selection.

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