Skip to main content
Glama

skycloak_get_realm_user

Read-only

Retrieve a specific Keycloak realm user by ID from a given cluster and realm, providing the user's stored details for lookups, audits, or access checks.

Instructions

Get a realm user by 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": {
      "cluster_id": "<cluster_id>",
      "realm": "<realm>",
      "user_id": "<user_id>"
    },
    "name": "skycloak_get_realm_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
user_idYesthe user ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
idYes
emailYes
enabledYes
usernameYes
last_nameNo
first_nameNo
email_verifiedYes

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 and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of behavior when the user or realm does not exist, no prerequisite/permission context, and no note on cluster scoping. The odd idempotentHint=false on a pure read is also left unexplained.

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 no padding or redundancy. It is concise to the point of being terse, but nothing in it is wasted.

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 not be explained, and all parameters are documented in the schema. What remains missing is behavioral context on failure modes and cluster/realm scoping, which matters for a lookup tool in a multi-tenant API.

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 coverage is 100% and each of the three parameters (cluster_id, realm, user_id) carries its own description. The description contributes only the vague notion of lookup 'by ID' and adds no format or scoping detail, so 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?

'Get a realm user by ID' states a specific verb and resource, and 'by ID' distinguishes it from the list-style sibling skycloak_list_realm_users. It does not name any sibling explicitly, so differentiation is inferential 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 Guidelines3/5

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

The phrase 'by ID' implies you already know the user ID and should use this rather than a list/search operation, but the description never states when to use this tool versus skycloak_list_realm_users or what to do if the ID is unknown. Usage is only implied.

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