Skip to main content
Glama

skycloak_remove_application_role

DestructiveIdempotent

Remove a role from an application's service account in a Keycloak realm to revoke its access. Identify the cluster, realm, client, and role to apply the change.

Instructions

Remove a role from an application's service account.

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

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
client_idYesthe application client ID receiving the role
role_nameYesthe role name
cluster_idYesthe cluster ID
role_client_idNoclient ID owning the role for a client role; omit for a realm role

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered elsewhere. The description contributes the useful scoping detail that the role is detached from the application's service account rather than from a user, which matters given siblings like skycloak_remove_realm_user_role, but it says nothing about error behavior or side effects.

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 redundant wording. It is efficient, though terse enough that the subject scope ('service account') is the only substantive content.

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?

For a destructive five-parameter mutation, the definition is minimally adequate: annotations carry destructiveness and idempotency, the schema is fully documented, and an output schema exists. However, nothing is said about preconditions (role must be assigned) or failure modes, leaving gaps an agent might care about before invoking a destructive call.

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 five parameters including the optional role_client_id are already documented in the schema. The description adds only the 'service account' framing, which reinforces the client_id semantics but does not explain the client-vs-realm role distinction itself.

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 states a concrete verb and resource — removing a role from an application's service account — which is specific enough to distinguish it from skycloak_assign_application_role and skycloak_delete_application_role. It does not explicitly name a sibling, so it stops short of a 5.

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 or when-not-to-use guidance and no mention of the complementary assign tool or of how this differs from delete_application_role. The only guidance is implicit in the verb 'remove'.

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