Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getgroupsgroupidmembers

getGroupsGroupIdMembers

Lists direct members of a Gerrit internal group; set recursive to include nested group membership.

Instructions

Lists the direct members of a Gerrit internal group.

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": {
      "group-id": "<group-id>"
    },
    "name": "getGroupsGroupIdMembers"
  }
}

Input Schema

NameRequiredDescriptionDefault
group-idYes
recursiveNo

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?

No annotations are supplied, so the description carries the full burden. It implies a read-only listing but says nothing about pagination, required permissions, whether members include owners, or how recursive expansion behaves — all material for an agent deciding whether one call suffices.

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. Brevity is appropriate, though the space saved could have carried the recursive explanation.

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 no explanation, but for a two-parameter group-membership tool the definition leaves the recursive flag and the accepted group-id format undocumented, which is the main risk of mis-invocation.

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 description explains neither parameter. 'Direct' hints that a recursive mode exists but never explains the recursive boolean, nor what identifier form group-id accepts (UUID, group name, or legacy numeric id).

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 gives a specific verb and resource ('Lists the direct members of a Gerrit internal group') and the word 'direct' implicitly separates it from member-detail and subgroup siblings. It is clear but does not explicitly name or contrast any sibling.

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 guidance on when to use this versus getGroupsGroupIdMembersMemberId or getGroupsGroupIdGroups, and no indication of when the recursive variant should be preferred. Usage is only inferable from the word 'direct'.

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