Skip to main content
Glama
Sign In
mcp-keycloak

mcp-keycloak

by dockndevai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List / search users

list_users
Read-onlyIdempotent

Retrieve users from a Keycloak realm with free-text search and pagination. Returns user details without passwords or secrets.

Instructions

List users in a realm. Supports free-text search and pagination. Passwords and secrets are never returned by Keycloak.

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

Input Schema

NameRequiredDescriptionDefault
maxNoMax results (default 50)
firstNoPagination offset
realmYesRealm name
searchNoFree-text search across username, email, first and last name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / first / maximum
      Added value: +9007199254740991
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds one genuinely useful behavioral fact – that passwords and secrets are never returned – but says nothing about pagination defaults, result ordering, or empty-result behavior.

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?

Three short sentences with no filler, and the core purpose is front-loaded ahead of the search/pagination note and the security caveat. Efficient, though the final sentence is somewhat tangential to tool selection.

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?

With no output schema, the description carries the burden of describing return values, and it only partially does so (it states what is never returned, not what a user record contains). For a simple read-only list tool with fully documented parameters, this is adequate but leaves the response shape unexplained.

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 four parameters (realm, max, first, search) are already documented with defaults and bounds in the schema. The description's mention of search and pagination adds no syntax, default, or format detail beyond that, so the baseline of 3 is appropriate.

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 states a specific verb and resource ('List users in a realm') plus the capabilities (free-text search, pagination), which is enough to separate it from get_user (single user) and count_users (aggregate count). It does not, however, explicitly name those siblings, so the differentiation is inferred 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?

The description asserts capabilities ('Supports free-text search and pagination') but never says when to use this tool instead of get_user or count_users, nor any exclusions or prerequisites. An agent must infer the routing decision from the names alone.

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