Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getgroups

getGroups

Lists Gerrit internal groups visible to the caller, with filters for user, project, ownership, visibility, and matching so you can find relevant groups.

Instructions

Lists the internal groups visible to the caller.

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

Input Schema

NameRequiredDescriptionDefault
ONo
oNo
userNo
groupNo
limitNo
matchNo
ownedNo
queryNo
regexNo
startNo
projectNo
suggestNo
owned-byNo
visible-to-allNo

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 burden; it only conveys that results are permission-scoped to the caller. Nothing is said about pagination (despite limit/start params), default ordering, or how filters interact — behavior a caller of a 14-parameter listing tool needs.

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 single sentence is front-loaded and free of filler, which is good structurally. However, the brevity here reflects under-specification rather than disciplined concision given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 14 optional parameters, zero schema documentation, no annotations, and no output schema, one sentence is wholly inadequate to call this tool correctly. An agent has no basis for choosing among the filter parameters or for paging results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 14 parameters (O, o, user, group, limit, match, owned, query, regex, start, project, suggest, owned-by, visible-to-all), and the description explains none of them. Cryptic single-letter parameters like 'O' and 'o' receive no clarification anywhere in the definition.

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 uses a specific verb plus resource ('Lists the internal groups') and adds a scope qualifier ('visible to the caller'), so an agent knows the shape of the result set. It does not distinguish this tool from siblings such as getAccountsAccountIdGroups or getGroupsGroupId, so an agent still cannot tell which getter to pick from the text alone.

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 exclusion of alternatives, and no prerequisites stated. The agent is left to infer that this is the top-level, unfiltered listing versus the numerous per-group and per-account siblings.

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