Skip to main content
Glama
idoyudha

mcp-keycloak

by idoyudha

remove_all_user_sessions

Terminate all active user sessions in a Keycloak realm to enforce immediate logout and reset authentication states.

Instructions

Remove all sessions for all users in the realm.

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

Returns:
    Status message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
realmNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'remove_all_user_sessions' tool. It is decorated with @mcp.tool(), which registers the tool. The function logs out all users in the specified realm by making a POST request to the Keycloak '/logout-all' endpoint.
    @mcp.tool()
    async def remove_all_user_sessions(realm: Optional[str] = None) -> Dict[str, str]:
        """
        Remove all sessions for all users in the realm.
    
        Args:
            realm: Target realm (uses default if not specified)
    
        Returns:
            Status message
        """
        await client._make_request("POST", "/logout-all", realm=realm)
        return {
            "status": "removed",
            "message": "Sessions for all users removed successfully",
        }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the action ('Remove all sessions') but fails to describe critical traits like whether this is destructive (likely yes, but not stated), permission requirements, rate limits, or what 'Status message' entails. This leaves significant gaps in understanding the tool's 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?

The description is appropriately sized and front-loaded, starting with the core action in the first sentence. The Args and Returns sections are structured clearly, though the 'Status message' return is vague. There's no wasted text, making it efficient for an agent to parse.

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 tool's complexity (a potentially destructive bulk operation) and lack of annotations, the description is incomplete—it doesn't cover permissions, side effects, or error handling. The presence of an output schema helps by indicating a return structure, but more context is needed for safe and effective use.

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 description adds minimal semantics beyond the input schema: it explains that 'realm' is the target and uses a default if unspecified. However, with 0% schema description coverage and only 1 parameter, this is adequate but not detailed—it doesn't clarify what a 'realm' is or provide examples, so it meets the baseline for low parameter count.

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 clearly states the verb ('Remove') and resource ('all sessions for all users in the realm'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'logout_user' or 'get_user_sessions', which handle individual user sessions rather than bulk removal.

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 like 'logout_user' for single users or other session management tools. It lacks context about prerequisites, such as requiring admin permissions or the impact of this action, leaving the agent without clear usage instructions.

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/idoyudha/mcp-keycloak'

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