Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccounts

getAccounts

Query Gerrit accounts visible to the caller, with filters, pagination, and optional extra fields.

Instructions

Queries accounts visible to the caller. The query is given by the query parameter; use limit and start to page and o to request extra fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getAccounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
ONo
oNo
limitNo
queryNo
startNo
suggestNo

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that results are scoped to accounts 'visible to the caller', which is genuine authorization context, and the word 'Queries' implies a non-destructive read. It omits rate limits, default page size, ordering, and whether paging is stable — gaps that matter for a paginated list tool.

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 tight sentences with the core purpose front-loaded and paging details after. Minor waste in the awkward phrasing 'and o to request extra fields', which reads like a fragment.

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?

An output schema exists, so return values need not be explained, and read-only intent is inferable. But for a 6-parameter, zero-coverage search tool with two undocumented and easily confused parameters ('o' vs 'O'), the definition leaves too much for the agent to guess.

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% across 6 parameters, so the description must compensate and only partly does. It mentions query, limit, start, and 'o' but leaves the distinct capital 'O' and 'suggest' entirely undocumented, never explains the query expression syntax, and 'o to request extra fields' is ambiguous about which fields or what format.

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 and resource with scope: 'Queries accounts visible to the caller'. The visibility scoping implicitly separates it from the many getAccountsAccountId* siblings, which target a single account, though no sibling is named explicitly.

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?

Explains procedurally how to call it ('the query is given by the query parameter'; use limit and start to page), which implies usage for a list/search endpoint. It never states when to prefer this over the per-account endpoints, nor any prerequisites for the query syntax.

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