Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidhead

getProjectsProjectIdHEAD

Retrieves the branch name that HEAD points to for a specified Gerrit project, helping identify its default branch.

Instructions

Retrieves for a project the name of the branch to which HEAD points.

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

Input Schema

NameRequiredDescriptionDefault
project-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden; it does convey that this is a pure retrieval whose output is a branch name, which establishes read-only semantics. However, it says nothing about required permissions, behavior on an empty repository or nonexistent project (likely 404), or any rate limits, leaving real gaps for a zero-annotation tool.

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 sentence with no filler, and the resource and returned value are front-loaded. The phrasing ("Retrieves for a project the name of the branch...") is slightly awkward but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value detail is not required, and the tool is simple with one parameter. What is missing is usage guidance and parameter format, which keeps it at minimum-viable rather than complete.

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%, so the lone project-id parameter depends entirely on the description, which only says "for a project." It does not clarify identifier format (numeric ID vs path/namespace) or whether the project must exist, so it does not compensate for the coverage gap.

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 ("Retrieves") with a specific resource (the branch name HEAD points to for a project), which is unambiguous. It does not differentiate itself from siblings such as getProjectsProjectId or getProjectsProjectIdBranches, which may also expose default-branch information, so it falls short of 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 statement of when to call this tool, when not to, or which sibling to prefer for related data (e.g., full branch metadata vs just HEAD). The only implied usage is 'get the default branch name', which an agent must infer.

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