Skip to main content
Glama

skycloak_download_theme_content

Read-only

Download a custom Keycloak theme's content archive by cluster and theme ID; returns archive size and SHA-256, inlining the archive only when small enough.

Instructions

Download a custom theme's content archive. Returns size and SHA-256 always, and the archive itself only when it is small enough to inline.

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_download_theme_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
theme_idYesthe theme ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
sha256Yes
inlinedYes
size_bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing conditional return behavior: size and SHA-256 are always returned, but the archive bytes only when small enough to inline. This is exactly the kind of context annotations (readOnlyHint/openWorldHint/idempotentHint) cannot convey. It stops short of saying what happens when the archive is too large (a download URL? an error?), leaving one behavioral gap.

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, front-loaded with the action and followed immediately by the return contract. No redundant restatement of the name or title.

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 fields need not be enumerated, and the description still usefully flags the inline-size condition. The one missing piece is the fallback path for oversized archives, which an agent would want to know before calling.

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?

With 100% schema description coverage, the schema already documents both cluster_id and theme_id. The description adds no extra meaning about parameter semantics, so the baseline applies.

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?

Description opens with a specific verb+resource: "Download a custom theme's content archive." That clearly distinguishes it from siblings like skycloak_update_theme_content or skycloak_get_theme, though it doesn't name them explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives (e.g. get_theme, update_theme_content) and no stated prerequisites such as permissions or whether the theme must be assigned. Usage is only implied by the verb.

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