Skip to main content
Glama

skycloak_get_realm_group

Read-only

Retrieve a Keycloak realm group by ID using its cluster and realm to inspect or manage a specific group.

Instructions

Get a realm group by ID.

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": {
      "cluster_id": "<cluster_id>",
      "realm": "<realm>",
      "group_id": "<group_id>"
    },
    "name": "skycloak_get_realm_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
group_idYesthe group ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not say what happens when the group ID is unknown, whether the lookup is scoped to the given cluster/realm, or which fields come back.

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 no wasted words and the identifying detail front-loaded. It is clean, though its brevity borders on under-specification rather than optimal economy.

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?

With an output schema present and annotations covering the safety profile, the description need not explain return values. Still, for a lookup tool with three required identifiers, the absence of any not-found or scoping behavior leaves a gap an agent may hit in practice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with all three required parameters documented in-schema, so the baseline is 3. The description adds no extra meaning about the cluster/realm/group ID relationship beyond what the schema already states.

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 ("Get a realm group") and adds the lookup key ("by ID"), which implicitly distinguishes it from the sibling list_realm_groups. It stops short of naming any sibling explicitly, so it sits just below the top tier.

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 prerequisites, and no named alternative. The phrase "by ID" hints that the caller must already hold an identifier, but the agent must infer that a list tool exists for discovery rather than being told.

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