Skip to main content
Glama

skycloak_get_cluster

Read-only

Retrieve full details for a single Keycloak cluster using its UUID. Use this to inspect cluster configuration and status by cluster ID.

Instructions

Get full details for a single Keycloak cluster by its 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": {
      "id": "<id>"
    },
    "name": "skycloak_get_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe cluster ID (UUID)

Output Schema

NameRequiredDescriptionDefault
idYes
urlNo
nameYes
sizeYes
typeYes
statusYes
versionYes
locationYes
created_atNo
updated_atNo
auto_upgrade_enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=false, and an output schema exists, so most of the behavioral burden is covered elsewhere. The description adds essentially nothing beyond that—no note on what 'full details' includes, error behavior for unknown IDs, or permission requirements.

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?

One short sentence with the resource and lookup key front-loaded; no filler or redundancy.

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?

For a single-parameter read tool with full schema coverage, annotations, and an output schema, the description supplies the essentials. It falls short only on routing guidance relative to the many cluster-specific sibling tools.

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?

There is a single parameter with 100% schema coverage, including a description specifying 'the cluster ID (UUID)'. The phrase 'by its ID' in the description merely restates the schema, so the baseline of 3 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?

The description states a specific verb and resource ('Get full details for a single Keycloak cluster') and names the lookup key ('by its ID'). It does not distinguish this tool from sibling cluster sub-resource getters such as skycloak_get_cluster_credentials or skycloak_get_cluster_security, so the agent must infer that this is the broad/primary cluster record.

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 when-to-use or when-not-to-use guidance and no mention of alternatives. Given the many sibling get_* tools in this family, a sentence like 'use this for the cluster's core configuration; use get_cluster_security for security settings' would be needed to reach a higher score.

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