Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidcommitscommitidin

getProjectsProjectIdCommitsCommitIdIn

Retrieves the branches and tags containing a given commit in a project, returning IncludedInInfo to show where the change is included.

Instructions

Retrieves the branches and tags in which a change is included. As result an IncludedInInfo entity is returned.

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>",
      "commit-id": "<commit-id>"
    },
    "name": "getProjectsProjectIdCommitsCommitIdIn"
  }
}

Input Schema

NameRequiredDescriptionDefault
commit-idYes
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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 supplied, so the description must carry the full behavioral burden. It does implicitly characterize the operation as a read ('Retrieves') and names the returned entity (IncludedInInfo), but says nothing about permissions, pagination of potentially long branch/tag lists, or behavior when the commit is unknown or not in the project. The output schema covers the return shape, which limits how much more is required here.

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?

Two short sentences with the core purpose front-loaded and no filler. The second sentence ('As result an IncludedInInfo entity is returned') is slightly awkward and, given an output schema exists, mostly redundant, but it is not harmful.

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?

The presence of an output schema means the return value does not need spelling out, and the core query is described. However, for a two-parameter lookup with zero schema coverage and no annotations, the definition should at minimum clarify the parameter roles and any format expectations; that gap keeps it at a minimum-viable level 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 both parameters are bare strings with no documentation in either schema or description. The description never explains that 'commit-id' identifies the change being queried and 'project-id' scopes the search, nor does it hint at accepted formats (short vs full SHA, path-encoded project IDs). This leaves the agent to infer the meaning of both inputs.

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: it retrieves the branches and tags that contain a given commit change. That is far more informative than the tautological title and would let an agent separate it from sibling lookups such as getProjectsProjectIdCommitsCommitIdDiff or getProjectsProjectIdCommitsCommitIdFiles. It never names the near-mirror sibling getProjectsProjectIdCommitsIn, so the distinction is clear in wording but not explicitly stated.

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 states what the tool returns but gives no guidance on when to prefer it over alternatives, despite sibling tools like getProjectsProjectIdCommitsIn covering what appears to be the inverse direction. It also omits any prerequisites, such as needing a commit hash from a prior lookup, and doesn't mention whether the input commit must belong to the given project.

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