Skip to main content
Glama
Sign In
keycloak-mcp-server

keycloak-mcp-server

by thebylito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list-events

Retrieve authentication and admin events from a Keycloak realm, with optional filters for event type and maximum results.

Instructions

Retrieve authentication and admin events

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

Input Schema

NameRequiredDescriptionDefault
maxNoMaximum results
typeNoEvent type filter
realmYesRealm name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description relies on the verb 'Retrieve' to imply a read-only, non-destructive operation. It does not explicitly mention safety characteristics or other behavior such as pagination or return format, but the action is clearly a read. This is minimally transparent.

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 of five words ('Retrieve authentication and admin events'), which is appropriately concise and front-loaded. It contains no fluff or redundant information, earning a perfect score.

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?

Given the simple nature of the tool and lack of output schema, the description is adequate but not complete. It does not explicitly state what is returned (e.g., a list), but the tool name 'list-events' implies a list. It covers the key purpose but leaves return details implicit.

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?

The schema description coverage is 100%, with all three parameters (realm, max, type) having descriptive text. The description adds no extra meaning to these parameters, so the baseline of 3 is appropriate per the calibration guidelines.

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 'Retrieve authentication and admin events' uses a specific verb ('Retrieve') and identifies the resource (authentication and admin events). It clearly distinguishes from sibling tools like 'clear-events' (which is destructive) and 'list-sessions' (which lists sessions), making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention conditions for use, exclusions, or reference other tools like 'clear-events' for event management. No context is given beyond the basic function.

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