create_realm
Create a new Keycloak realm by submitting a realm representation object with custom settings.
Instructions
Create a new realm.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| realm_data | Yes | Realm representation |
Create a new Keycloak realm by submitting a realm representation object with custom settings.
Create a new realm.
| Name | Required | Description | Default |
|---|---|---|---|
| realm_data | Yes | Realm representation |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It only says 'Create a new realm,' which implies a write operation but discloses no behavioral traits (e.g., permissions required, idempotency, side effects). The description is insufficient for understanding behavioral impact.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, making it very concise. However, it is too brief for a creation tool, lacking necessary detail. Every word is used, but the overall information value is low.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of creating a realm (nested object parameter, no output schema), the description is incomplete. It fails to explain the return value, success criteria, or validation rules. Sibling tools provide ample context, but this description does not leverage it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% because the sole parameter 'realm_data' has a description 'Realm representation,' but the tool description adds no additional meaning. No details on expected fields, structure, or examples are provided, leaving the parameter poorly specified.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Create a new realm,' which specifies the verb and resource. It distinguishes from sibling tools like get_realm, update_realm, delete_realm. However, it provides no additional context about what a realm is or its structure.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. No mention of prerequisites, consequences, or context. Sibling tools include many realm operations, but the description offers no usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/paoloamato2/keycloak-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server