Skip to main content
Glama

skycloak_list_user_groups

Read-only

Retrieve the groups a user belongs to in a Keycloak realm, given the cluster ID, realm name, and user ID, to audit or verify role-based access assignments.

Instructions

List the groups a user belongs to.

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>",
      "user_id": "<user_id>"
    },
    "name": "skycloak_list_user_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
user_idYesthe user ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
countYes
groupsYes

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. The description adds nothing beyond that scope phrase — it does not say whether indirect/inherited group memberships are included, how empty results behave, or whether results are paginated, despite an output schema existing.

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 zero wasted wording and the key scope up front. It is efficient, though the brevity borders on under-specification rather than tight editing.

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?

For a simple three-parameter read with full schema coverage, annotations, and an output schema, the description covers the essentials. It is only minimally adequate because it leaves the boundary with the realm-level group listing tools unaddressed, which is the main way an agent could pick the wrong tool.

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 (cluster_id, realm, user_id) documented inline, so the schema carries parameter meaning fully. The description contributes no additional semantics such as whether user_id accepts a username or only an internal ID, 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?

The description gives a specific verb and resource ('List the groups') and scopes it to a single user ('a user belongs to'), which distinguishes it from the realm-level group listing sibling. It does not name any sibling explicitly, so differentiation is left partly implicit.

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 or when-not-to-use guidance and no reference to alternatives such as skycloak_list_realm_groups or skycloak_list_user_roles. The agent must infer from the sentence alone that this is the per-user lookup rather than the realm-wide group listing.

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