Skip to main content
Glama

skycloak_get_theme_assignment

Read-only

Retrieves the active custom theme assigned per Keycloak theme type, such as login, account, admin, or email, for a specified realm and cluster.

Instructions

Get the active custom theme per Keycloak theme type (login, account, admin, email) for a realm.

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

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=false, so the agent knows the safety profile without the description. The description adds genuine context by enumerating the theme types covered (login, account, admin, email) and clarifying that only the *active custom* theme is returned, distinguishing it from settings or theme content retrieval; it does not say what happens when no custom theme is assigned.

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?

A single front-loaded sentence with the resource and its scope stated before the qualifying enumeration. No filler, no redundancy.

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?

With two required, fully documented parameters, an output schema in place, and annotations covering safety, the description supplies enough to invoke the tool correctly. The only gap is the unstated behavior when a realm has no custom theme assigned for a given type.

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 both parameters (realm, cluster_id) are already documented in the schema and the baseline applies. The description adds nothing beyond the schema for parameters — 'for a realm' merely restates the realm parameter's role.

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 ('Get'), a specific resource ('active custom theme'), and constrains the granularity ('per Keycloak theme type ... for a realm'). The realm-level scoping implicitly separates it from skycloak_get_client_theme_assignment, but that sibling is never named, so differentiation is inferred rather than stated.

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?

Usage is only implied by the scoping phrase 'for a realm' — an agent can reason that client-scoped lookups belong elsewhere, but no when-to-use condition, prerequisite, or explicit alternative is given. Adequate for a simple getter, but not a routing aid.

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