Skip to main content
Glama

skycloak_list_realms

Read-only

List Keycloak realms in a Skycloak cluster, or across every cluster in your workspace when no cluster ID is provided.

Instructions

List the Keycloak realms in a Skycloak cluster.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idNothe cluster whose realms to list. Omit to list realms across every cluster in the workspace

Output Schema

NameRequiredDescriptionDefault
countYes
realmsYes
unreachableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 no behavioral context beyond the structured fields - no mention of pagination, ordering, or what a workspace-wide (omitted cluster_id) listing entails - which is acceptable but not value-adding.

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?

One short sentence, front-loaded with verb and resource, with no filler or redundancy. It is efficient, though arguably terse for a tool whose scope can vary from one cluster to the whole workspace.

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 not be described, and the sole parameter is fully documented in the schema. Combined with annotations covering the read-only nature, the definition is nearly complete; only explicit differentiation from sibling list tools is missing.

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 a single optional parameter at 100% schema description coverage, the schema already explains that omitting cluster_id widens the listing to every cluster. The description adds nothing beyond that, so the baseline 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 uses a specific verb (List) and resource (Keycloak realms in a Skycloak cluster), so an agent immediately knows what it returns. It does not name a sibling or state how it differs from tools like skycloak_list_realm_roles or skycloak_list_clusters, which keeps it below 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 Guidelines3/5

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

Usage is only implied: the resource scope ('realms in a Skycloak cluster') hints at when to reach for this over other list tools. There is no explicit when-to-use/when-not guidance or named alternative, though the optional-cluster behavior is carried by the schema rather than the description.

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