Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidhashtags

getChangesChangeIdHashtags

Retrieves the hashtags associated with a Gerrit change by its change ID, so you can inspect or filter changes by label.

Instructions

Gets the hashtags associated with a change.

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>"
    },
    "name": "getChangesChangeIdHashtags"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 behavioral burden. 'Gets' implies a read-only operation, but the description does not disclose permission requirements, behavior when the change is missing, or response characteristics beyond what the output schema may cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single clear sentence with no filler or redundancy. The purpose is front-loaded and appropriately sized for a simple getter.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity tool with one parameter and an output schema, the description is minimally adequate: it identifies what is returned and the resource it is tied to. It still leaves usage context and parameter semantics largely unexplained, which limits completeness.

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 the single required 'change-id' parameter. The description only says the hashtags are 'associated with a change,' which is essentially restated by the parameter name and adds no format, scope, or example semantics.

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 ('Gets') and resource ('the hashtags associated with a change'), so the tool's purpose is immediately clear. It does not explicitly distinguish itself from sibling tools, but the 'hashtags' resource is unique among the listed siblings.

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?

Usage is implied: call this tool when hashtags for a specific change are needed. There is no explicit when-to-use guidance, no exclusions, and no mention of alternatives, which is a gap for a tool sitting alongside many other change-related getters.

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