Skip to main content
Glama

skycloak_delete_application_role

Destructive

Delete an application role and revoke it from every user and group holding it; set confirm=true to proceed.

Instructions

Delete a role from an application. Every user and group holding it loses it. 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>",
      "client_id": "<client_id>",
      "role_name": "<role_name>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_application_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
confirmYesmust be true to confirm deletion
client_idYesthe application's OAuth client ID
role_nameYesthe 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

A3.8/5.0
Behavior4/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 covered. The description still earns credit by disclosing the blast radius — every user and group holding the role loses it — which is a consequence the annotations do not convey. It misses the related fact that a repeat call will fail rather than no-op, which matters given idempotentHint=false.

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

Conciseness5/5

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

Three short sentences, zero filler, with the destructive consequence and the confirmation requirement both front-loaded before any other detail. Every sentence carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the safety profile, so the description's job is mainly consequence disclosure, which it does well. It is slightly thin on edge behavior — no mention of what happens if the role is absent or of irreversibility — but nothing essential for a correct call is missing.

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%, so all five parameters (including confirm) are already documented in the schema. The description restates only that confirm must be true, adding no new meaning about identifiers, formats, or cross-parameter relationships. Baseline 3 is appropriate.

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?

Names a specific verb and resource plus a scope qualifier ("from an application"), so the agent can tell this deletes an application-scoped role entity rather than an assignment. It does not distinguish itself from the easily confused sibling skycloak_remove_application_role (unassign) or skycloak_delete_realm_role, leaving the closest alternatives ambiguous.

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 procedural guidance is the confirm=true precondition, which reads as an execution gate rather than a when-to-use rule. There is no statement of when to choose delete vs remove vs update, nor any exclusion such as "use this only when the role should no longer exist at all." Usage is implied by the destructive wording rather than stated.

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