keycloak-mcp-server

get-user

Retrieves user details by ID from a specified Keycloak realm. Provides account information for a given user ID.

Instructions

Get user details by ID from a specific 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": {
      "realm": "<realm>",
      "userId": "<userId>"
    },
    "name": "get-user"
  }
}

Input Schema

Name	Required	Description	Default
`realm`	Yes	Realm name
`userId`	Yes	User ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It indicates a read operation ('Get'), which is non-destructive, but it does not disclose behavior such as possible errors, return format, or whether the operation is read-only. The description is not misleading, but it adds minimal behavioral context beyond what the tool name implies.

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?

The description is a single sentence that immediately states the verb, resource, and parameters. It is front-loaded and contains no filler or redundant phrasing. Every word earns its place.

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 simple getter tool with two parameters and no output schema, the description is mostly complete. It specifies the lookup criteria (realm, userId) and the general purpose. However, it could be slightly more explicit about what 'user details' includes (e.g., profile attributes, roles, etc.), though the sibling context and schema partially compensate.

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%: the schema already explains 'realm' as 'Realm name' and 'userId' as 'User ID'. The description's 'from a specific realm' slightly reinforces the realm's role, but it does not add meaning beyond the schema. Baseline is 3 due to high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get'), names the resource ('user details'), and adds the scoping mechanism ('by ID from a specific realm'). This clearly distinguishes it from sibling tools like list-users and search-users, which have broader or different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description implies when to use this tool: when you have a known user ID and realm. It does not explicitly state when not to use it or name alternatives, but the context is clear given the tool's getter nature and the sibling set. No exclusions are mentioned, but the specificity of 'by ID' and 'from a specific realm' provides sufficient guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server