Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidbranchesbranchidreflog

getProjectsProjectIdBranchesBranchIdReflog

Fetch branch reflog entries for a Gerrit project and branch, filtered by timestamp range or limit, to audit branch changes and trace revisions.

Instructions

Gets the reflog of a certain 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": "getProjectsProjectIdBranchesBranchIdReflog"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
branch-idYes
project-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 of behavioral disclosure. 'Gets' implies a read-only operation, and the output schema can cover return values, but the description does not mention pagination, ordering, permissions, or how from/to/limit affect results.

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 description is a single waste-free sentence with the core operation front-loaded. It is concise and readable, though its brevity contributes to the missing parameter and usage detail.

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 tool with five parameters, no annotation coverage, and no schema descriptions, the definition is too sparse. The output schema may cover return values, but the input semantics and usage context are largely left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are five input parameters with 0% schema description coverage, and the description explains none of them. It does not clarify what from, to, or limit mean, nor how project-id and branch-id scope the reflog query.

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 states a specific verb and resource: getting the reflog of a branch. It is clearly distinguishable from sibling branch tools such as branch details, files, or mergeability checks, though it does not explicitly name alternatives.

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?

It gives no explicit guidance on when to use this tool versus related branch tools, nor any exclusions or prerequisites. The intended usage is only implied by the phrase 'reflog of a certain branch.'

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