Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getgroupsgroupidgroupssubgroupid

getGroupsGroupIdGroupsSubgroupId

Retrieves a specific subgroup within a Gerrit group by group ID and subgroup ID, enabling targeted group hierarchy lookup.

Instructions

Retrieves a subgroup.

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>",
      "subgroup-id": "<subgroup-id>"
    },
    "name": "getGroupsGroupIdGroupsSubgroupId"
  }
}

Input Schema

NameRequiredDescriptionDefault
group-idYes
subgroup-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/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 behavioral burden. "Retrieves" weakly implies a read-only fetch, but nothing is said about authentication, whether the subgroup must belong to the given group, or what happens when either ID is invalid. An output schema exists, so return-value detail is not required here.

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 short sentence is front-loaded and wasteful only in the sense of being nearly empty. It is not verbose, but its brevity comes from under-specification rather than disciplined editing.

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?

Given two mandatory undocumented parameters, no annotations, and a hierarchical resource (subgroup nested under a group), the description is not complete enough to call the tool confidently. The presence of an output schema excuses return-value explanation but not the missing input and scoping context.

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 two required parameters, so the description must compensate and does not. It never explains that group-id identifies the parent group and subgroup-id the nested subgroup, nor what ID format (numeric, slug, path) is expected, leaving both parameters semantically empty.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Retrieves a subgroup" restates the resource implied by the name getGroupsGroupIdGroupsSubgroupId in readable form, but adds no distinguishing detail. It does not say how this differs from siblings like getGroupsGroupIdGroups (likely the subgroup listing) or getGroupsGroupId, so an agent cannot route between them 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 Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no named alternatives. The description gives the agent nothing about the conditions under which this tool is the right choice versus its many sibling getters.

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