Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getgroupsgroupidgroups

getGroupsGroupIdGroups

Lists the direct subgroups of a specified Gerrit group, enabling you to inspect group hierarchy and membership structure.

Instructions

Lists the direct subgroups of a 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": "getGroupsGroupIdGroups"
  }
}

Input Schema

NameRequiredDescriptionDefault
group-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose a real behavioral trait beyond the schema — results are limited to direct (immediate) subgroups rather than the full hierarchy — but says nothing about access requirements, pagination, or behavior for groups with no subgroups, leaving meaningful gaps for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the scoping qualifier front-loaded and no redundant restatement of the title or name. Nothing in the wording could be cut without losing meaning.

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?

The existence of an output schema means return values need not be described, and the tool is a simple single-parameter read, so the bar is modest. Still, with no annotations and an undocumented parameter, an agent lacks guidance on identifier expectations and result-set behavior that the description could have covered in one more clause.

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 schema has one required parameter (group-id) with 0% description coverage and no enums, and the description adds no meaning at all about it — no indication of where the group-id comes from or what identifier form it takes. With low schema coverage the description should compensate, and it does not.

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 names a specific verb and resource ("Lists the direct subgroups of a group") and the word "direct" meaningfully narrows scope versus a recursive listing. It does not explicitly distinguish itself from the sibling getGroupsGroupIdGroupsSubgroupId, which retrieves one subgroup, but the verb/resource pairing is clear enough to distinguish on intent.

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?

Usage is only implied: an agent can infer this is used when it has a group-id and wants its child groups. There is no explicit when-to-use statement, no exclusion of recursive/descendant traversal, and no named alternative for fetching a single subgroup.

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