Skip to main content
Glama

skycloak_delete_theme

Destructive

Deletes a custom theme only after explicit confirmation, helping remove unused themes while blocking deletion of themes still assigned to a realm.

Instructions

Delete a custom theme. Set confirm=true to proceed. To change an existing theme's files, use skycloak_update_theme_content instead: deleting a theme that is still assigned returns 409, and re-uploading it gives a new ID.

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>",
      "theme_id": "<theme_id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesmust be true to confirm deletion
theme_idYesthe theme ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely new context: the confirm gate, the 409 failure when the theme is still assigned, and that re-uploading yields a new ID rather than restoring the old one. It stops short of saying whether the theme's files are irrecoverably purged or whether assignments must be cleared first as a prerequisite step.

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 the action, then the safety gate, then the alternative and its failure mode. Every sentence carries distinct information and nothing is repeated.

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?

An output schema exists, so return values need no explanation. For a destructive three-parameter delete, the definition covers the confirmation requirement, the alternative tool, and the 409 error path — everything an agent needs to call it 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%, so all three parameters (cluster_id, theme_id, confirm) are already documented. The description repeats the confirm=true requirement without adding syntax or format detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ('Delete a custom theme') and immediately distinguishes it from the file-editing sibling skycloak_update_theme_content. An agent can tell it apart from update_theme_content, get_theme, and the assignment tools without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent away from this tool when the intent is modifying theme files ('use skycloak_update_theme_content instead'), and adds the blocking condition that an assigned theme returns 409. That is both a when-to-use and a when-not-to-use rule, plus a consequence of ignoring it.

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