Skip to main content
Glama

skycloak_set_client_theme_assignment

Idempotent

Set a client's login-theme override in a Keycloak realm using a theme ID, or clear it with an empty string to restore the realm default.

Instructions

Set a client's login-theme override. Pass a theme ID, or an empty string to reset to the realm default.

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

Input Schema

NameRequiredDescriptionDefault
loginNotheme ID for the client login page; empty resets to the realm default
realmYesthe Keycloak realm name
client_idYesthe application client ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
loginYes

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?

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful reset-to-realm-default behavior, a non-obvious side effect. It does not address what happens when the optional "login" parameter is omitted entirely, which is a real ambiguity given login is not in the required list.

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?

Two short sentences, front-loaded with the primary action and then the reset alternative. No filler, no restatement of the title.

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?

This is a low-complexity mutation with four fully documented parameters and an output schema, so the description does not need to explain return values. The only material gap is the undefined behavior when the optional login parameter is omitted.

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%, including the exact note that an empty login value resets to the realm default, so the description's parameter guidance duplicates the schema rather than extending it. No semantics are added for cluster_id, realm, or client_id. 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?

The description uses a specific verb plus scoped resource: "Set a client's login-theme override." This is clearly distinct from the realm-level sibling skycloak_set_theme_assignment, though the sibling is never named so the distinction must be inferred from "client's" and "realm default".

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?

It gives one concrete usage rule — pass a theme ID to set, or an empty string to reset to the realm default — which implies when to choose each mode. It offers no explicit statement of when to use this tool rather than the realm-level theme tools, and the sibling get tool is never mentioned.

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