Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidbranches

getProjectsProjectIdBranches

Lists branches for a specified Gerrit project and returns BranchInfo entities, with optional filters and pagination to find the branches you need.

Instructions

Lists the branches of a project as BranchInfo entities.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
matchNo
regexNo
startNo
project-idYes
next-page-tokenNo

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 supplied, so the description carries the full burden, and it discloses almost nothing beyond the basic operation: no pagination behavior despite limit/start/next-page-token parameters, no statement about filtering or ordering, and no permission requirements. The only behavioral hint is the BranchInfo return entity, which the output schema already covers.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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, paginated list operation with no annotations, the description should at minimum explain paging and the match/regex filters. Return values are covered by the output schema, but the input-side behavior an agent needs to call this correctly is missing.

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, and the description only implicitly maps the project scope (project-id). It says nothing about what limit, start, match, regex, or next-page-token do, leaving the paging and filtering semantics entirely undocumented.

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 uses a specific verb and resource ("Lists the branches of a project") and hints at the return type (BranchInfo entities), which is enough to distinguish it from the single-branch sibling getProjectsProjectIdBranchesBranchId. It stops short of explicitly naming that sibling or stating the collection-vs-single distinction.

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 when to prefer this over getProjectsProjectIdBranchesBranchId, and no prerequisites or auth context. The agent must infer usage 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