Skip to main content
Glama

skycloak_get_realm_role

Read-only

Retrieves a Keycloak realm role by name from a specified cluster and realm, helping you inspect role details without manual lookup.

Instructions

Get a realm role by name.

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

Input Schema

NameRequiredDescriptionDefault
nameYesthe role name
realmYesthe Keycloak realm name
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
nameYes
compositeYes
descriptionNo

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, openWorldHint=false, and idempotentHint=false, so the safety profile is covered elsewhere. The description adds nothing beyond that: it does not say what happens if the role is missing (empty result vs. error), nor anything about permissions or lookup semantics.

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 short sentence, front-loaded with the verb and resource, with zero filler. It is efficient, though it is on the terse side for a lookup tool with three required identifiers.

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?

The tool is simple, all parameters are schema-documented, and an output schema exists, so return values need not be explained. However, with no note on missing-role behavior or on how this differs from the list/application-role variants, the definition is only minimally complete.

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?

Schema description coverage is 100%, so all three parameters are already documented in the schema, which sets the baseline at 3. The phrase "by name" confirms that name is the lookup key rather than a filter, a small but real addition over the schema.

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?

"Get a realm role by name" names a specific verb (get), a specific resource (realm role), and the lookup key (name). This distinguishes it implicitly from sibling write operations like create/update/delete_realm_role, but it never explicitly addresses the nearby alternatives such as list_realm_roles or get_application_role.

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 at all: no mention of when to prefer this over list_realm_roles or get_application_role, and no stated preconditions (e.g., that the role must already exist or that cluster_id/realm must resolve first). The agent must infer usage purely from the name.

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