Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidwatchedprojects

getAccountsAccountIdWatchedProjects

Retrieves all projects a specified Gerrit account is watching, using the account ID to return that account's watched project list.

Instructions

Retrieves all projects a user is watching.

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": "getAccountsAccountIdWatchedProjects"
  }
}

Input Schema

NameRequiredDescriptionDefault
account-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It says 'all projects' but never states whether results are paginated, whether the caller must be that user or merely have read access, or whether watching data is private. Only the bare retrieval semantics are conveyed, with none of the operational context a mutation-free but permission-sensitive endpoint needs.

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?

One short, front-loaded sentence with no filler or repetition. Brevity is appropriate, though the extreme terseness leaves needed detail unstated.

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 values need not be explained, but that is the only burden lifted. With zero annotation coverage, an undocumented required parameter, and an undefined relationship between 'user' and the account-id path, the definition is too thin for an agent to call it confidently in edge cases.

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 'account-id' parameter, and the description never mentions it at all. It does not clarify that account-id identifies the user whose watched projects are returned, nor what format the identifier takes, so it fails to compensate for the schema gap.

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?

States a specific verb ('Retrieves') and resource ('all projects a user is watching'), so the intent is immediately graspable. It loses a point because it says 'a user' while the tool is account-scoped via an account-id parameter, leaving a small ambiguity about whose watch list is returned, and it does nothing to distinguish itself from the many other account-scoped getters.

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 prerequisites, and no mention of alternatives or related endpoints. The agent is left to infer that this is a read of the authenticated account's watched-project list 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