Skip to main content
Glama

skycloak_add_realm_user_to_group

Idempotent

Add a user to a specific group within a Keycloak realm to grant group-based access and permissions. Requires cluster ID, realm name, user ID, and group ID.

Instructions

Add a user 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>",
      "user_id": "<user_id>",
      "group_id": "<group_id>"
    },
    "name": "skycloak_add_realm_user_to_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
user_idYesthe user ID
group_idYesthe group ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no mention of what happens if the user is already a member, no permission/authorization requirements, no error or partial-failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words and the action front-loaded, but the brevity comes at the cost of any structure or added information. It is minimal rather than efficient.

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 and the input schema fully documents all parameters, so the description needn't explain return values. However, for a cross-resource mutation (cluster + realm + user + group) it omits preconditions and edge-case behavior that would help an agent call it correctly.

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 four required parameters documented, so the schema carries parameter meaning. The description does not add semantics such as whether user_id/group_id are Keycloak UUIDs versus names, so baseline 3 applies.

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 verb (Add) and a resource (user to a realm group), but it is essentially a restatement of the tool name with 'skycloak' and underscores stripped. It does not clarify scope (e.g., that it is a Keycloak group-membership mutation on a cluster/realm) or distinguish it from adjacent operations beyond what the name already conveys.

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 the inverse tool (skycloak_remove_realm_user_from_group), and no statement of preconditions such as the user and group already existing. The agent must infer everything from the name.

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