Skip to main content
Glama

skycloak_list_realm_roles

Read-only

List realm-scoped roles in a Keycloak realm by cluster ID and realm name, so you can review or manage permissions within that realm.

Instructions

List the realm-scoped roles in a realm.

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

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
countYes
rolesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 without description help. The description adds nothing further: no word on pagination, result volume, ordering, or whether a missing realm yields an error or an empty list. For a read-only list tool this is a low bar, and the text clears none of it.

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?

A single front-loaded sentence with no filler or repetition. It is appropriately sized for the little it conveys, though its brevity comes at the cost of information rather than being a model of efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 no explanation, and annotations plus full schema coverage carry the safety and parameter burden. What remains missing is guidance on scope selection against sibling role-listing tools and any note on pagination or result limits, leaving the definition minimally viable.

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 schema description coverage at 100%, both cluster_id and realm are already documented in the schema, so the baseline of 3 applies. The description does not add format hints, constraints, or an explanation of why both identifiers are required together.

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 names a specific verb ('List') and resource ('realm-scoped roles in a realm'), and the qualifier 'realm-scoped' implicitly separates it from application- and user-scoped role listings. It stops short of explicitly naming siblings such as skycloak_list_application_roles, so the differentiation is suggestive rather than stated.

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 guidance, no prerequisites, and no mention of alternatives, despite the sibling catalog containing several other role-listing tools where scope selection matters. An agent must infer from the name alone that 'realm-scoped' means this is the right choice over application or user role listings.

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