Skip to main content
Glama

skycloak_assign_realm_user_role

Idempotent

Assign a Keycloak realm role to a user by specifying the cluster, realm, user ID, and role name. This grants role-based access in that realm.

Instructions

Assign a realm role to a user.

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>",
      "role_name": "<role_name>"
    },
    "name": "skycloak_assign_realm_user_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
user_idYesthe user ID
role_nameYesthe realm role name
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

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=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and retry profile is known. The description adds nothing beyond that: it doesn't say whether re-assigning is a no-op, what happens if the role doesn't exist, or what permissions are needed. An output schema exists, so return values need not be explained, but the mutation semantics remain unaddressed.

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 zero wasted words. It is efficient, but the brevity borders on under-specification given the tool's mutation semantics.

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?

The schema is complete and annotations plus an output schema cover safety and returns, so the minimum for correct invocation is present. Missing are prerequisites for a role-assignment mutation (existence of user and role, duplicate assignment behavior), which would make it sufficient rather than merely adequate.

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 each of the four parameters documented in the schema itself. The description only restates 'realm' and 'role' as parameters without adding format, constraints, or relationships, so it meets the baseline without adding value.

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 uses a specific verb and resource ('Assign a realm role to a user'), and the term 'realm role' implicitly separates it from skycloak_assign_application_role. It stops short of explicitly naming or contrasting with that sibling, so it is clear but not fully differentiating.

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 statement of prerequisites (the role and user presumably must already exist), and no mention of the closely related alternatives such as assign_application_role or remove_realm_user_role. The agent must infer the selection context entirely 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