Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeideditchangeeditidmeta

getChangesChangeIdEditChangeEditIdMeta

Retrieve metadata for a file in a Gerrit change edit by change ID and edit ID, returning available web links.

Instructions

Retrieves meta data of a file from a change edit. Currently only web links are 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": {
      "change-id": "<change-id>",
      "change-edit-id": "<change-edit-id>"
    },
    "name": "getChangesChangeIdEditChangeEditIdMeta"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes
change-edit-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the current output limitation (only web links), implying a read-only retrieval, but says nothing about permissions, error behavior, or whether the metadata set may expand.

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 action front-loaded and the output caveat immediately after. Nothing is redundant, though the sentence could have been spent on parameter or usage detail instead.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 explained, and the description covers the essential caveat about what is returned. The remaining gap is the absence of usage context relative to closely named siblings.

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% for two required parameters, but 'change-id' and 'change-edit-id' are self-describing identifiers in this API family. The description adds no meaning beyond their names, leaving the 0%-coverage gap essentially unfilled.

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 ('Retrieves meta data of a file from a change edit') and scopes the result ('currently only web links are returned'), which an agent can distinguish from the sibling getChangesChangeIdEditChangeEditId. It does not explicitly name a sibling to differentiate against, keeping it below 5.

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 use this tool versus the many sibling edit-related endpoints (e.g., getChangesChangeIdEditChangeEditId, getChangesChangeIdMetaDiff). The agent must infer usage from the narrow 'web links' scope 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