Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getgroupsgroupidoptions

getGroupsGroupIdOptions

Retrieve configuration options for a Gerrit group by group ID to inspect its settings and available permissions before managing membership or access.

Instructions

Retrieves the options 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": "getGroupsGroupIdOptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
group-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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 behavioral burden and delivers almost nothing: it does not say whether a group-id must exist, whether this is safe/read-only, whether the response is a list of options or a flag map, or what permissions might be required. It at least implies a read operation via "Retrieves", which is the only behavioral signal present.

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?

A single short sentence with the resource front-loaded and no filler; the problem is under-specification, not verbosity. It is structured appropriately for what little it says.

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?

Although an output schema exists (so return-value shape needn't be explained) and there is only one simple parameter, the core ambiguity of what "options" contains is unresolved. For a tool whose entire identity hinges on an undefined term, the definition is not complete enough to invoke confidently.

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% for the sole parameter, group-id, so the description must compensate and does not — "of a group" only loosely gestures at it. It adds no format, ID-source, or scoping information beyond what the schema's property name already conveys.

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

Purpose3/5

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

The description names a verb ("Retrieves") and a resource ("options of a group"), so it is more than a bare restatement of the tool name. However, "options" is never defined — it could mean group configuration flags, sub-options, or settable properties — leaving the agent unable to distinguish its payload from siblings like getGroupsGroupIdDetail or getGroupsGroupIdDescription.

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 call this tool, no mention of prerequisites, and no comparison to the many sibling getGroupsGroupId* read tools. The single sentence offers no criteria an agent could use to choose this over getGroupsGroupId or getGroupsGroupIdDetail.

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