Skip to main content
Glama

skycloak_update_application_role

Idempotent

Rename an application role or change its description in a Keycloak realm; omitted fields keep their current values.

Instructions

Rename an application role or change its description. Fields you omit keep their current value.

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_update_application_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
new_nameNorename the role to this
client_idYesthe application's OAuth client ID
role_nameYesthe role to change
cluster_idYesthe cluster ID
descriptionNonew description

Output Schema

NameRequiredDescriptionDefault
idNo
nameYes
client_idYes
compositeYes
client_uuidNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare that this tool is a non-destructive, idempotent write operation in a closed system, so the safety profile is covered. The description adds one genuinely useful non-annotated detail: merge semantics, where omitted fields keep their current value and are not cleared. It says nothing, however, about the side effects of renaming, such as how existing role assignments or references behave after the name changes.

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?

There are two short sentences with no wasted words. The primary action comes first, followed by the patch-semantics caveat, which is exactly where an agent needs to read it.

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?

Because an output schema exists, the description does not need to explain return values. For a six-parameter, fully documented mutation tool, the description covers what the tool changes and how partial input is handled. The only real gap is the consequence of a rename for existing assignments.

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%, and every parameter, including realm, client_id, role_name, new_name, and description, is already documented in the schema. The description only adds the general rule that omitted fields retain their current value, rather than any per-parameter syntax or format detail. A baseline of 3 is appropriate when the schema does the heavy lifting.

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 specific verb (rename / change description) on a specific resource (an application role), which lets an agent separate it from sibling operations like skycloak_create_application_role or skycloak_assign_application_role. It does not explicitly distinguish itself from the closely named skycloak_update_realm_role, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies its usage as the way to modify an existing role, and the 'fields you omit keep their current value' line tells the agent that a minimal call is valid. However, it names no alternatives and gives no exclusions, so it does not say when an agent should pick skycloak_update_realm_role rather than this tool.

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