Skip to main content
Glama

skycloak_create_realm_role

Creates a realm-scoped role in a Keycloak realm on a specific cluster, enabling permission definitions for users or groups within that realm.

Instructions

Create a realm-scoped role.

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

Input Schema

NameRequiredDescriptionDefault
nameYesthe role name
realmYesthe Keycloak realm name
cluster_idYesthe cluster ID
descriptionNooptional role description

Output Schema

NameRequiredDescriptionDefault
nameYes
compositeYes
descriptionNo

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, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds nothing beyond that: it does not say what happens if the role already exists, whether it overwrites, or what permissions are required.

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 redundancy. Its brevity is efficient, though it borders on under-specification rather than crisp conciseness.

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?

Complexity is low, the input schema is fully documented, an output schema exists, and annotations cover the safety profile, so the bare description is minimally sufficient. It still leaves out failure modes and the realm/role relationship an agent might need before calling it.

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 coverage is 100%, with all four parameters individually documented, including that 'description' is optional. The description adds no meaning beyond the schema, which is the expected baseline when the schema does the work.

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 plus resource, 'Create a realm-scoped role', which unambiguously identifies the operation. The 'realm-scoped' qualifier hints at the contrast with application-role creation, but the description never names or rules out that sibling explicitly.

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 guidance on when to use this tool versus skycloak_create_application_role or skycloak_assign_realm_user_role, and no mention of prerequisites such as needing the realm to exist. The only signal is implicit in the word 'Create'.

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