Skip to main content
Glama

skycloak_update_theme

Idempotent

Update a theme’s name, description, or version metadata in Skycloak without replacing its archive; use the content update tool to replace archives.

Instructions

Update a theme's name, description, or version. Metadata only: use skycloak_update_theme_content to replace the theme's archive.

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>"
    },
    "name": "skycloak_update_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNonew name
versionNonew version
theme_idYesthe theme ID
cluster_idYesthe cluster ID
descriptionNonew description

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
statusYes
versionNo
file_sizeYes
theme_typesYes
restart_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful scope framing ("metadata only"), but for a mutation tool it omits important behavior: whether omitted fields are left unchanged or cleared, and whether renaming to an existing name errors. Those gaps matter more than the safety profile here.

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?

Two short sentences, zero filler, with the scope constraint front-loaded before the pointer to the alternative tool. Nothing could be removed without losing routing information.

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?

An output schema exists so return values need no explanation, and the params are fully documented. Given the tool's simplicity, the definition is nearly complete; the only shortfall is the unstated partial-update and naming-conflict semantics, which would help an agent invoke 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 every parameter (name, version, theme_id, cluster_id, description) is already documented in the schema. The description merely lists the same updatable fields in prose without adding format, constraint, or validation meaning. Baseline 3 applies.

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+resource (update a theme's name, description, or version) and immediately bounds the scope with "Metadata only," naming the sibling tool that handles archive content. An agent can distinguish this from skycloak_update_theme_content without opening either schema.

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?

Explicitly routes archive replacement to skycloak_update_theme_content, which is the key ambiguity for an "update theme" tool. It does not address the other adjacent operations (theme settings, assignments), but those live under clearly different verbs, so the guidance is clear if not exhaustive.

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