Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getchangeschangeidattention

getChangesChangeIdAttention

Retrieve the users currently in a Gerrit change's attention set to identify who needs to review or act.

Instructions

Returns all users that are currently in the attention set. As response a list of AttentionSetInfo entity is 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>"
    },
    "name": "getChangesChangeIdAttention"
  }
}

Input Schema

NameRequiredDescriptionDefault
change-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; 'Returns' does signal a read-only operation and it names the returned entity, which is meaningful behavioral context. However, it omits permission/visibility requirements for attention-set data, behavior for nonexistent or closed changes, and whether the result can be empty.

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, front-loaded with the purpose, with no filler. The second sentence partly duplicates what the output schema already conveys, but it costs little and confirms the entity shape.

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?

This is a simple one-parameter read tool with an output schema, so the description needn't explain return values, and it covers purpose adequately. The notable gap is the undocumented change-id parameter and the absence of any annotation-substitute safety or permission context.

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% and the single required parameter change-id is not mentioned at all in the description. An agent can guess from context that change-id identifies the Gerrit change, but the description adds no format, validation, or scoping meaning beyond the bare property name.

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 ('Returns all users') and a specific domain resource ('currently in the attention set'), plus the response entity type (AttentionSetInfo). It is clearly distinguishable from sibling endpoints such as comments, reviewers, or messages without opening a schema, though it names no explicit alternative.

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 when-to-use guidance, no mention of prerequisites or permissions, and no comparison to alternatives such as Reviewer or ChangeDetail endpoints. The agent must infer that this endpoint is for inspecting who is currently flagged in the attention set.

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