Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidcommitscommitidfilesfileidcontent

getProjectsProjectIdCommitsCommitIdFilesFileIdContent

Retrieves the content of a file from a specific commit in a Gerrit project using project, commit, and file identifiers.

Instructions

Gets the content of a file from a certain commit.

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>",
      "file-id": "<file-id>"
    },
    "name": "getProjectsProjectIdCommitsCommitIdFilesFileIdContent"
  }
}

Input Schema

NameRequiredDescriptionDefault
file-idYes
commit-idYes
project-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not say whether the content comes back as raw or base64 text, whether size limits or binary files apply, or what happens for a deleted or binary path. With no annotation coverage, a single sentence is thin behavioral disclosure for a content-returning 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?

It is one short sentence with zero filler, and the key scoping detail (the commit) comes first. Brevity here costs it substance, not clarity.

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?

There is an output schema, so the return shape does not need to be explained. Even so, for a file-content endpoint the description should say how the content is encoded and whether large or binary files are handled, and none of that is present.

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% for all three required parameters. The description only maps loosely to file-id and commit-id, and it never mentions project-id or any ID format expectations, so it fails to compensate for the missing schema documentation.

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?

States a specific verb and resource — 'Gets the content of a file' — plus the scope, 'from a certain commit.' That scope does implicitly separate it from the branch-based sibling getProjectsProjectIdBranchesBranchIdFilesFileIdContent, but the description never names or contrasts an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Saying the content comes 'from a certain commit' implies when to use it, namely when you have a commit ID rather than a branch. There is no explicit when-to-use or when-not guidance and no alternatives are named.

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