Skip to main content
Glama

skycloak_set_theme_assignment

Idempotent

Assign custom Keycloak themes to a realm by type (login, account, admin, email), using a theme ID to activate or an empty string to reset to default while changing only provided fields.

Instructions

Assign custom themes to a realm per Keycloak theme type. Pass a theme ID to activate it, or an empty string to reset that type to Keycloak's built-in default. Only the provided fields are changed.

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": "skycloak_set_theme_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
adminNotheme ID for the admin console; empty string resets to the Keycloak default
emailNotheme ID for email templates; empty string resets to the Keycloak default
loginNotheme ID for the login page; empty string resets to the Keycloak default
realmYesthe Keycloak realm name
accountNotheme ID for the account console; empty string resets to the Keycloak default
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
adminNo
emailNo
loginNo
accountNo

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 readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: omitted theme-type fields are left untouched ('Only the provided fields are changed') and an empty string reverts to the built-in default rather than clearing the type. It does not mention authorization requirements or what happens if a supplied theme ID does not exist.

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, front-loaded with what the tool does, then the two value conventions, then the partial-update guarantee. No filler or repetition of the schema.

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 and rich annotations carry much of the burden, and the description covers activation, reset and partial-update semantics. It omits the practical prerequisite that themes must already exist in the realm (see skycloak_get_theme/skycloak_download_theme_content) and does not distinguish this realm-scoped tool from the client-scoped sibling, which matters for correct selection among 30+ tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the per-parameter descriptions already explain the empty-string reset for admin, email, login and account. The description still adds meaning beyond the schema by stating the partial-update contract for the optional theme-type fields, which the schema only implies via required=[cluster_id, realm].

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?

States a specific verb and resource ('Assign custom themes to a realm') and scopes it to Keycloak theme types, which implicitly separates it from the client-level variant in the sibling list. It does not name any sibling outright, 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 Guidelines3/5

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

Gives clear operational guidance for the two modes of use: pass a theme ID to activate, or an empty string to reset that type to the Keycloak default. It never says when to reach for this versus skycloak_get_theme_assignment or skycloak_set_client_theme_assignment, so routing is left to inference from the words 'realm' and 'assign'.

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