Skip to main content
Glama

skycloak_get_client_theme_assignment

Read-only

Retrieve a client's login-theme override in a Keycloak realm; an empty result indicates the realm default applies.

Instructions

Get a client's login-theme override (empty means 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_get_client_theme_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: an empty return means the realm default is in effect, which prevents misreading an empty response as an error. It does not cover permission requirements or how the override resolves against the realm theme.

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 no filler; the parenthetical adds meaning rather than noise. Every clause earns its place.

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 an output schema present, return values need no explanation, and all three required parameters are documented, so the short description is close to sufficient for this narrow read tool. The only meaningful omission is a pointer to the realm-level or setter siblings, which would help an agent route correctly.

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%, with realm, client_id, and cluster_id each documented in the schema itself, so the baseline of 3 applies. The description adds no syntax, format, or scoping detail about these identifiers beyond what the schema already provides.

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 names a specific verb and resource ("Get a client's login-theme override") and the parenthetical clarifies what an empty result means, so the operation is unambiguous. It stops short of explicitly distinguishing itself from the sibling realm-level get/set theme tools, which the name implies but the text never states.

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 guidance, no mention of prerequisites, and no named alternative such as the realm-scoped theme assignment getter or the setter counterpart. The only interpretive help is the note that an empty value falls back to the realm default, which is output semantics rather than usage routing.

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