Skip to main content
Glama

skycloak_get_theme_settings

Read-only

Retrieves a workspace's theme naming policy to show whether exact theme folder names are enforced and whether served theme paths remain stable after content replacements.

Instructions

Get the workspace's theme naming policy: whether exact_theme_names is on. When on, every theme in the workspace is served from a folder named exactly like the theme, and that name never changes across content replaces. When off (the default), the served folder changes on each content replace, unless the theme was created by a platform migration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "skycloak_get_theme_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
exact_theme_namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context the annotations cannot: the default is off, 'on' pins the served folder to the theme name permanently across content replaces, and even when off, migration-created themes keep a stable folder. That is substantive semantic disclosure beyond structured fields.

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?

The key fact (which setting is returned) is front-loaded, and the two explanatory clauses about on/off behavior each carry distinct information about served folder naming. It is slightly dense and could be split for readability, but no sentence is 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?

With zero parameters and an output schema present, the description only needs to frame what is being read and how to interpret it — both are done, including the off-state default and the migration exception. Nothing an agent needs in order to call and interpret this tool is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description stays focused on interpreting the result rather than inventing parameter guidance.

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?

The first clause gives a specific verb+resource ('Get the workspace's theme naming policy') and immediately names the exact field it reports ('whether exact_theme_names is on'). That is enough to distinguish it from siblings such as skycloak_update_theme_settings (which writes the policy) and skycloak_get_theme (which fetches a theme's content).

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the read companion to update_theme_settings, but the description never says so, nor does it state when the policy actually matters to a caller. No exclusions or explicit alternatives are given; the reader must connect the dots from the sibling names.

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