Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidcommitsin

getProjectsProjectIdCommitsIn

Find which refs contain specified commits by returning a map of each commit to the full ref names where it was merged.

Instructions

Gets refs in which the specified commits were merged into. Returns a map of commits to sets of full ref names.

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": "<commit>",
      "ref": "<ref>"
    },
    "name": "getProjectsProjectIdCommitsIn"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
commitYes
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 full behavioral burden. It discloses the return shape as a map of commits to full ref names and 'Gets' implies a read-only operation, but it does not mention permissions, rate limits, error behavior, or whether the ref input narrows the result.

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 short and front-loads the operation before stating the return shape. It is efficient, though the phrase 'merged into' and the unexplained relationship with the ref input make it slightly ambiguous.

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?

An output schema exists, so the description does not need to fully explain return values. However, with three required parameters at 0% schema description coverage and no annotations, the definition is missing essential input semantics and usage context for reliable invocation.

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 description should compensate for the undocumented parameters. It references commits and refs conceptually but does not explain the required commit array, required ref array, or project-id parameter, nor clarify whether ref is an input filter or part of the lookup scope.

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 refs in which specified commits were merged, returning a map of commits to ref sets. This is clear enough to distinguish the tool from generic commit-detail siblings, though it does not explicitly name how it differs from getProjectsProjectIdCommitsCommitIdIn.

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 explains what the tool returns but gives no guidance on when to use it versus related commit or ref tools. It provides no exclusions, prerequisites, or alternative-tool routing.

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