Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidrevisionsrevisionidfilesfileidblame

getChangesChangeIdRevisionsRevisionIdFilesFileIdBlame

Retrieve blame information for a file at a specific revision of a Gerrit change to identify which commits last modified each line.

Instructions

Gets the blame of a file from a certain revision.

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": {
      "change-id": "<change-id>",
      "revision-id": "<revision-id>",
      "file-id": "<file-id>"
    },
    "name": "getChangesChangeIdRevisionsRevisionIdFilesFileIdBlame"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNo
file-idYes
change-idYes
revision-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 supplied, so the description bears the full burden, yet it only implies a read operation. It says nothing about the effect of the unexplained 'base' flag, authentication requirements, or result size, leaving the agent to guess at behavior beyond the return shape covered by the output schema.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is part of the reason other dimensions are under-specified.

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 four-parameter tool with no annotations and zero schema coverage, the definition is too thin; the unexplained 'base' flag and the lack of behavioral context leave the agent under-informed. The existing output schema covers return values, but input-side and usage context remain incomplete.

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

Parameters3/5

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

Schema description coverage is 0% across four parameters, so the description must compensate; it only loosely hints at 'file' and 'revision' without mapping them to file-id or revision-id. The 'change-id' and especially the boolean 'base' parameter receive no explanation at all, which is a meaningful gap.

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 names a specific verb ('Gets') and resource ('the blame of a file from a certain revision'), so an agent can grasp that this returns line-attribution data for a file snapshot. It does not, however, distinguish the tool from close siblings like FileIdContent, FileIdDiff, or FileIdDownload, which all operate on the same file-at-revision resource.

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 guidance on when to choose blame over content, diff, or download, and no mention of prerequisites or exclusions. The agent must infer the use case entirely from the word 'blame'.

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