Skip to main content
Glama
Sign In
mcp-keycloak

mcp-keycloak

by idoyudha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

remove_all_user_sessions

Clear all active user sessions in a Keycloak realm, forcing immediate logout for all users.

Instructions

Remove all sessions for all users in the realm.

Args:
    realm: Target realm (uses default if not specified)

Returns:
    Status message

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remove_all_user_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are present, so the description carries full burden. It states removal of all sessions but omits behavioral traits like irreversibility, effect on active users, or authentication status. This is insufficient for a potentially destructive operation.

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?

Extremely concise: two sentences plus structured Args/Returns. Every phrase provides value, and the main action is front-loaded.

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?

Given the simple tool (one param, output schema exists for return), the description is adequate. However, for a destructive action, a bit more behavioral context (e.g., impact on users) would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning to the 'realm' parameter by explaining it targets the realm and uses a default if unspecified. Since schema description coverage is 0%, this compensates well for the single optional parameter.

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 'Remove all sessions for all users in the realm' with specific verb and resource scope. It distinguishes from siblings like 'logout_user' (single user) and 'get_user_sessions' (list only).

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 provides basic context (realm parameter defaults) but no explicit when-to-use or alternatives. It neither says when not to use nor compares with related tools.

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