Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidstarredchanges

getAccountsAccountIdStarredChanges

Retrieves the changes a specific user account has starred with the default star, helping you find their tracked reviews and followed work in Gerrit.

Instructions

Gets the changes that were starred with the default star by the identified user account.

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": {
      "account-id": "<account-id>"
    },
    "name": "getAccountsAccountIdStarredChanges"
  }
}

Input Schema

NameRequiredDescriptionDefault
account-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about authentication needs, whether results are paginated or bounded in time, or whether only the caller's own account is permitted. The phrase 'default star' implies a notion of other/named stars that is never explained, leaving a real behavioral ambiguity.

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 well-formed sentence with no filler or redundancy. It is tightly worded, though its brevity is achieved by omitting rather than by front-loading the key facts.

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?

An output schema exists, so return shape need not be described. But with no annotations, an undocumented parameter, and an undefined 'default star' concept, the definition leaves an agent without enough information to invoke this safely or to distinguish it from adjacent change- and account-scoped 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?

The single parameter has 0% schema description coverage, so the description must compensate. It only implies that the id identifies a user account; it gives no format, does not clarify whether the value is a numeric id, username, or 'self', and does not say whether the starred changes of any account or only one's own can be fetched.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description has a verb ('Gets') and a resource ('changes that were starred with the default star'), but neither term is grounded: 'changes' is a domain-specific object and 'default star' is never defined, so an agent cannot be certain what is returned. It gives no signal distinguishing this from sibling endpoints such as getChangesChangeId or getChangesChangeIdAttention.

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 statement of when to use this tool, when not to, or which sibling to prefer. The only implicit scoping is 'by the identified user account', which does not tell an agent how to choose between this and the many other account-scoped 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