Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidlabels

getProjectsProjectIdLabels

List labels defined in a Gerrit project, optionally including inherited labels or those voteable on a ref. Use this to inspect label configuration for review setup.

Instructions

Lists the labels that are defined in this project.

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": "getProjectsProjectIdLabels"
  }
}

Input Schema

NameRequiredDescriptionDefault
inheritedNo
project-idYes
voteable-on-refNo

Output Schema

NameRequiredDescriptionDefault
resultNo

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 provided, so the description carries the full burden of behavioral disclosure. It does not explain whether inherited labels are returned, how the filters affect results, whether pagination exists, or what permissions are needed for this read operation. 'Defined in this project' hints at scoping but does not fully clarify behavior.

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?

The definition is a single front-loaded sentence with no wasted wording. It is concise to the point of under-specification, but the structure itself is clear.

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?

The presence of an output schema reduces the need to describe return values. However, for a list operation with three parameters, zero schema coverage, and no annotations, the description is too thin: it omits filtering semantics, pagination, and the meaning of the non-required parameters.

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%, leaving all three parameters undocumented in the schema. The description only contextualizes the required project-id parameter through the phrase 'in this project'; it adds no meaning for the 'inherited' or 'voteable-on-ref' parameters. This is a significant gap for a tool with filters.

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 clearly states a specific verb and resource: it lists the labels defined in a project. It is distinguishable from the sibling detail tool that retrieves a single label by ID. However, it does not explicitly name that sibling or clarify scope boundaries such as inherited labels.

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?

The description gives no explicit guidance on when to use this tool versus alternatives, nor when not to use it. The verb 'Lists' implies a collection-retrieval use case, but the agent must infer that on its own.

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