Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getgroupsgroupidowner

getGroupsGroupIdOwner

Retrieves the owner group of a Gerrit internal group by group ID, helping you identify group ownership and manage access.

Instructions

Retrieves the owner group 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": "getGroupsGroupIdOwner"
  }
}

Input Schema

NameRequiredDescriptionDefault
group-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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. 'Retrieves' correctly signals a read-only operation and the 'internal group' qualifier usefully scopes the behavior, but nothing is said about permissions required, what happens for non-internal groups, or error/empty-result behavior.

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; the resource is stated immediately. It is efficiently written, though its brevity leaves semantic gaps that belong to other dimensions.

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 tool is simple (one parameter) and an output schema exists, so return values need no explanation. However, with an undescribed schema parameter, the description should at least characterize the group-id format and the internal-group constraint's consequences to be fully actionable.

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 single parameter 'group-id' has 0% schema description coverage, and the description does not compensate by explaining the accepted identifier form (numeric legacy ID, UUID, or group name). An agent must guess the expected format for the only required input.

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 ('Retrieves') and a specific resource ('the owner group of a Gerrit internal group'), which is clearly distinguishable from sibling getters such as getGroupsGroupIdMembers, getGroupsGroupIdName, or getGroupsGroupIdDetail. It stops short of explicitly naming those siblings, but the resource is unambiguous.

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: you call it when you need the owner of a group. The phrase 'Gerrit internal group' hints at a prerequisite (the tool applies to internal groups, not external/LDAP-backed ones), but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance.

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