Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getgroupsgroupidname

getGroupsGroupIdName

Retrieves the name of a Gerrit group by its group ID, helping you resolve group identifiers to readable names.

Instructions

Retrieves the name 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": "getGroupsGroupIdName"
  }
}

Input Schema

NameRequiredDescriptionDefault
group-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 and discloses almost nothing: only that it reads a name. It does not state whether the call is read-only (implied but unstated), what happens for an unknown or inaccessible group id, or what fields the response contains beyond the name.

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 sentence, front-loaded and free of filler. It is efficient, but the terseness is under-specification rather than disciplined conciseness given the missing parameter and behavior details.

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?

An output schema exists, so return values need not be explained, and the tool is genuinely simple with one required parameter. Still, the description omits the group-id format and the behavior on missing/inaccessible groups, which is thin for a tool with no annotations to fall back on.

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 required parameter 'group-id' has 0% schema description coverage, and the description adds no meaning about it — not its format (numeric vs. slug), where an agent would obtain it, or how it is validated. With one undocumented parameter, the description needed to compensate and does not.

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 states a specific verb and resource ('Retrieves the name of a group'), so the basic action is clear. However, it does nothing to separate this from closely named siblings such as getGroupsGroupIdDescription or getGroupsGroupId, leaving the agent to infer that this returns only the name field rather than the group object or its description.

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 when-to-use guidance, no mention of prerequisites (e.g., permissions or knowing a valid group id), and no reference to alternatives. The agent gets a purpose statement but nothing about when this tool is the right choice over its many siblings.

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