Skip to main content
Glama
mrz1880

mcp-keycloak-admin

by mrz1880
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List login events

keycloak_events_login
Read-onlyIdempotent

Retrieve recent user login events from Keycloak to audit authentication activity or investigate failed logins. Returns a JSON array of events, optionally filtered by type or user.

Instructions

Read-only. Returns recent user login events from the realm's login event log (such as LOGIN, LOGIN_ERROR, and LOGOUT), as a JSON array ordered by the event log's default ordering. Use this to audit authentication activity or investigate failed logins; for administrative changes (user/role/config updates) use keycloak_events_admin instead. This tool is idempotent and never modifies Keycloak.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNoMaximum number of login events to return. Integer between 1 and 500. Defaults to 20 when omitted.
typeNoOptional Keycloak login event type to filter by, e.g. 'LOGIN', 'LOGIN_ERROR', or 'LOGOUT'. When omitted, events of all types are returned.
userNoOptional Keycloak user ID (UUID) to restrict results to a single user. When omitted, events for all users are returned.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Description states read-only, idempotent, and never modifies Keycloak, consistent with annotations. Adds ordering context.

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?

Three clear sentences, front-loaded with 'Read-only', no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers use cases, output format, ordering, and safety. No gaps given annotations and schema.

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%, description does not add meaning beyond schema. Baseline 3.

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?

Clearly states action (returns), resource (login events), and scope (realm's login event log). Differentiates from sibling keycloak_events_admin.

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

Usage Guidelines5/5

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

Explicitly tells when to use (audit, investigate failed logins) and when not (use keycloak_events_admin for admin changes).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrz1880/mcp-keycloak-admin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server