Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidtopic

getChangesChangeIdTopic

Retrieves the topic assigned to a Gerrit change using its change ID, helping identify the change's associated topic.

Instructions

Retrieves the topic of 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": "getChangesChangeIdTopic"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior on its own, and it discloses almost nothing. It does not say whether the call needs authentication or read permission, what happens when a change has no topic assigned (empty string vs. error vs. null), or whether the result is scoped to the caller. The presence of an output schema covers the return shape, but the operational behavior is undocumented.

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

Conciseness3/5

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

The sentence is short and front-loaded with no filler, but its brevity is under-specification, not efficiency. It reads as a label rather than a useful definition.

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?

This is a simple, one-parameter read tool with an output schema, so the description does not need to explain the return values. Even so, it omits the change-id format and what happens when no topic exists, and both are things an agent needs before calling it in a crowded family of change sub-resource tools.

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?

There is only one parameter, change-id, and schema description coverage is 0%, so the description must explain the parameter, but it does not. It does not say whether the id is numeric, a Change-Id string like 'I8473b959...', or a project~branch~id triplet, so the agent gets no help choosing a value.

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 gives a specific verb and resource: 'Retrieves the topic of a change.' That is enough for an agent to tell it apart from siblings such as getChangesChangeIdMessage and getChangesChangeIdHashtags, which fetch different sub-resources of the same change. It loses a point only because it never says what a 'topic' is in this system, so the term stays opaque.

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?

The description gives no guidance about when to use this tool rather than one of the many sibling getChangesChangeId* tools, and no prerequisites or exclusions. The agent must infer usage purely from the name.

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