Skip to main content
Glama

skycloak_list_realm_group_members

Read-only

List the users that belong to a realm group in a Skycloak cluster. Retrieve group members by cluster ID, realm name, and group ID to audit or manage access.

Instructions

List the users that belong to a realm 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": {
      "cluster_id": "<cluster_id>",
      "realm": "<realm>",
      "group_id": "<group_id>"
    },
    "name": "skycloak_list_realm_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
group_idYesthe group ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
countYes
usersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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, and an output schema exists to describe the result. The description adds no behavior beyond that: it does not say whether members are paginated, whether nested subgroups are included, or how the group is resolved within the realm. With the annotation baseline met, a 3 fits.

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 front-loaded sentence with no filler or repetition. It is efficient, though so brief that it leaves gaps for the other dimensions to cover.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a scoped list tool with full schema coverage, annotations, and an output schema, the description is almost enough for an agent to call it correctly. The only real omission is whether subgroup members are included, which is a minor detail.

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%: all three required parameters (cluster_id, realm, group_id) are documented in the schema itself. The description adds no extra parameter meaning, so the baseline of 3 applies.

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 and resource: 'List the users that belong to a realm group.' This clearly separates it from skycloak_list_realm_users (all users) and skycloak_get_realm_group (group metadata), though it never names those siblings.

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 by the object it returns: use it when you need members of one group. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to the complementary tools like skycloak_add_realm_user_to_group or skycloak_remove_realm_user_from_group.

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