Skip to main content
Glama

skycloak_update_theme_settings

DestructiveIdempotent

Toggle a workspace's exact theme naming policy on or off so themes serve from folders matching their names; requires an owner or admin API key and confirm=true.

Instructions

Turn the workspace's exact_theme_names policy on or off. The caller's API key must have been minted for a workspace owner or admin; any other role, including a cluster admin, gets 403 even with themes:write. Turning it on moves every existing theme in the workspace to its exact served name in the background, not blocking this call; a theme that cannot move right away (its cluster is busy updating, say) moves on its next content replace instead. Turning it off changes nothing immediately: each theme keeps its current served folder until its next content replace, after which the folder changes on every replace again. A theme replaced under its exact name sets restart_required=true on skycloak_get_theme and skycloak_list_themes until Keycloak restarts; use skycloak_restart_cluster_instances to apply it. Set confirm=true to proceed.

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": {
      "exact_theme_names": "<exact_theme_names>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_update_theme_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesmust be true to confirm the change, which moves every theme in the workspace and needs a workspace owner or admin key
exact_theme_namesYestrue to serve every theme from a folder named exactly like the theme; false for the default, changing folder per content replace

Output Schema

NameRequiredDescriptionDefault
exact_theme_namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes far beyond the annotations: discloses that enabling migrates themes asynchronously in the background without blocking the call, that themes on busy clusters defer until their next content replace, that disabling changes nothing immediately, and that a replace under the exact name sets restart_required=true until a cluster restart. It also spells out the auth failure mode (403) and the confirm gate, which annotations alone (destructiveHint/idempotentHint) could never convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but every sentence carries operational information, and the core action plus permission constraint are front-loaded ahead of the asynchronous-behavior detail. The on/off semantics could be split more explicitly for scanability, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, two-parameter settings toggle with an output schema and full annotation coverage, the description supplies everything an agent needs: authorization constraints, async/delayed effects, the confirm requirement, and the restart path that resolves restart_required.

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 baseline is 3, but the description adds real meaning beyond the schema by explaining the concrete consequences of each boolean value — background migration when turning on, deferred per-replace folder change when turning off — rather than restating 'true to serve every theme from a folder named exactly like the theme'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb ('Turn ... on or off') and a specific resource scoped precisely to the workspace-level 'exact_theme_names policy', which separates it from the theme-mutating siblings like skycloak_update_theme that operate on individual themes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Clearly states the authorization prerequisite (workspace owner/admin key, 403 for anyone else including cluster admins with themes:write) and routes the agent to skycloak_get_theme / skycloak_list_themes and skycloak_restart_cluster_instances for follow-up. It does not explicitly name a sibling to use instead for reading the current policy value, but the context for when to call this is clear.

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