Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidcommitscommitid

getProjectsProjectIdCommitsCommitId

Retrieve a specific commit from a project using its project ID and commit ID to inspect commit details and metadata.

Instructions

Retrieves a commit of a project.

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

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

C2.4/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 of behavioral disclosure, and it discloses nothing: not whether this is a read-only operation (implied only by 'Retrieves'), not what authorization or visibility scope applies, and not how missing or unknown commit ids are handled. This is a significant gap for a tool with zero annotation coverage.

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 short sentence with no padding or redundancy, and the core verb is front-loaded. It is appropriately sized in the literal sense, though the brevity comes at the cost of substance rather than from efficient information density.

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 return values need not be described, but for a two-required-parameter tool with no annotations and no schema descriptions, the definition leaves the agent without format requirements, behavioral expectations, or sibling disambiguation. It is under-specified relative to even modest complexity.

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 must compensate for both parameters, and it does not. It never explains the expected format of 'project-id' or 'commit-id' (numeric vs. path-encoded string, full vs. short SHA), which is exactly the kind of detail the schema leaves empty.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ('Retrieves') and resource ('a commit of a project'), which is more than a bare restatement of the title, but it adds almost nothing beyond what the tool name getProjectsProjectIdCommitsCommitId already conveys. It offers no differentiation from close siblings such as getProjectsProjectIdCommitsCommitIdDiff or getProjectsProjectIdCommitsCommitIdFiles, so an agent cannot tell from the text whether this returns commit metadata versus a diff or file list.

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 stated prerequisite (e.g., needing both a project id and commit id resolved first), and no mention of alternatives for related needs. The agent must infer everything about selection from the name alone.

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