Skip to main content
Glama
idoyudha

mcp-keycloak

by idoyudha
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_accessible_realms

Retrieve the list of accessible realms in Keycloak for identity and access management configuration.

Instructions

Get accessible realms.

Returns:
    List of accessible realms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/tools/realm_tools.py:9-18 (handler)
    The handler function for the 'get_accessible_realms' MCP tool. It is decorated with @mcp.tool() for registration and fetches accessible realms using the KeycloakClient's _make_request method.
    @mcp.tool()
async def get_accessible_realms() -> List[Dict[str, Any]]:
    """
    Get accessible realms.

    Returns:
        List of accessible realms
    """
    return await client._make_request("GET", "/realms", skip_realm=True)

Tool Definition Quality

C2.3/5.0
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 states the tool returns a list of accessible realms, which implies a read-only operation, but doesn't clarify what 'accessible' means (e.g., based on permissions, authentication, or filtering). It lacks details on authentication requirements, rate limits, error conditions, or pagination. The description is minimal and doesn't provide adequate behavioral context for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two short sentences, but it's under-specified rather than efficiently informative. The first sentence restates the name, and the second adds minimal value by stating the return type. While it avoids waste, it lacks the depth needed for clarity, making it feel incomplete rather than optimally brief.

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 has 0 parameters, 100% schema coverage, and an output schema exists (which covers return values), the description doesn't need to explain parameters or return details. However, it's a read operation with no annotations, and the description fails to provide sufficient context about what 'accessible realms' entails or how it differs from siblings. It's minimally adequate but has clear gaps in purpose and usage guidance.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to compensate for any parameter gaps, as there are none. It appropriately doesn't discuss parameters, which aligns with the schema. A baseline of 4 is given since no parameters exist and the schema fully covers them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get accessible realms' is essentially a tautology that restates the tool name without adding meaningful specificity. It doesn't explain what 'accessible realms' means in this context, what constitutes accessibility, or how this differs from other realm-related tools like 'get_realm_info' or 'list_realms' (though the latter doesn't exist in the sibling list). The description lacks a clear verb+resource distinction from siblings.

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

Usage Guidelines1/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. There are multiple realm-related tools in the sibling list (e.g., 'get_realm_info', 'update_realm_settings'), but the description doesn't explain how this tool differs or when it's appropriate. No context, exclusions, or alternatives are mentioned.

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