Skip to main content
Glama

skycloak_delete_realm_role

Destructive

Deletes a Keycloak realm role from a specified cluster and realm; set confirm=true to proceed with the removal.

Instructions

Delete a realm role. Set confirm=true to proceed.

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

Input Schema

NameRequiredDescriptionDefault
nameYesthe role name
realmYesthe Keycloak realm name
confirmYesmust be true to confirm deletion
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is known without the description. The description adds the confirm-gate as a behavioral requirement, but says nothing about irreversibility, what happens to existing user/group role mappings, or required permissions.

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?

Two short sentences, front-loaded with the action, and free of filler. The second sentence duplicates what the schema already says about confirm, so a small amount of the text is not strictly earning its place.

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, so return values need not be explained, and parameters are fully covered by the schema. For a destructive, non-idempotent operation, however, the description omits consequences and side effects (e.g., impact on role assignments) that would round out the picture.

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%, so all four parameters (cluster_id, realm, name, confirm) are already documented in the schema. The description only restates the confirm semantics already present in the schema, adding no new meaning about identifier formats or scoping.

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?

"Delete a realm role" gives a specific verb plus resource, and the realm-vs-application distinction is carried by the tool name against siblings like skycloak_delete_application_role. It is clear and unambiguous, though the description itself doesn't explicitly contrast it with 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?

The only usage guidance is the prerequisite that confirm must be set to true. There is no statement of when to choose this over related tools such as update_realm_role or delete_realm, nor any note that the role must exist or that assignments are affected.

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