keycloak-mcp-server

get-user-attributes

Retrieve all user attributes for a Keycloak user by realm and user ID, including unmanaged attributes.

Instructions

Get user attributes including unmanaged attributes

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

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

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. The verb 'Get' implies a read-only operation, and 'including unmanaged attributes' adds useful context about the return scope. However, it does not specify permissions, error behavior, or what constitutes 'unmanaged', leaving some gaps.

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, succinct sentence that is front-loaded with the key action and includes the most important differentiator without any wasted words.

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?

The tool is simple with two well-documented params and no output schema, but the description covers the essential purpose and the unique 'unmanaged attributes' scope. It lacks details on response format or permissions, but for a simple getter it is nearly 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% for both parameters (realm and userId), and the description adds no additional parameter-level semantics. Baseline of 3 is appropriate as the schema already documents the parameters clearly.

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 clearly states the tool's function with a specific verb ('Get') and resource ('user attributes'), and the qualifier 'including unmanaged attributes' distinguishes it from sibling tools like 'get-user' and 'get-group-attributes'.

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 description implies this tool is for retrieving user attributes, especially when unmanaged attributes are needed, but it does not explicitly state when to use it over alternatives or provide exclusion criteria.

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

Deploy Server