Skip to main content
Glama

skycloak_list_themes

Read-only

Lists custom themes uploaded to a cluster, including their IDs, status, and theme types, so you can check which themes are available and whether a restart is required.

Instructions

List the custom themes uploaded to a cluster, with their IDs, status, and theme types. restart_required is true on a theme whose replaced content is not live yet; see skycloak_get_theme_settings and skycloak_restart_cluster_instances.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
countYes
themesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 real value by explaining that restart_required means replaced theme content is not yet live, which is behavioral context not present in annotations or schema. It does not address result size, pagination, or whether all themes are returned unfiltered, so it remains partial.

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 sentences, front-loaded with what the tool returns; the second sentence handles the one non-obvious field and the follow-up tools. No filler, and the see-also pointers are compact rather than listy.

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-value documentation is not required, and annotations cover the safety profile — the description supplies the one non-obvious field interpretation plus follow-up routing. It omits result-volume or empty-list behavior, which is a minor gap for a simple single-parameter list tool.

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 coverage is 100% for the single cluster_id parameter, so the schema already carries the required semantics. The description adds no scope or format detail about cluster_id (e.g., what happens with an invalid cluster or whether child clusters are included). Baseline 3 is appropriate given the schema does the work.

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 first sentence gives a specific verb and resource — 'List the custom themes uploaded to a cluster' — plus the returned fields (IDs, status, theme types). It is clearly distinguishable from skycloak_get_theme_settings, which it names as a follow-up rather than an alternative. It stops short of an explicit 'use this instead of X when...' routing statement, so a 4 rather than a 5.

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?

The description establishes a concrete workflow: list themes here, then follow up with skycloak_get_theme_settings or skycloak_restart_cluster_instances when restart_required signals stale content. That is clear context and implicit next-step guidance. There are no explicit exclusions or preconditions for when this tool is inappropriate, which keeps it from a 5.

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