Skip to main content
Glama

skycloak_create_application

Create OIDC or SAML client applications in a Keycloak realm and return the client secret for confidential clients. Store the secret immediately, because it cannot be retrieved later.

Instructions

Create an OIDC/SAML client (application) in a realm. Returns the client secret for confidential clients (store it; it is not retrievable later).

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": {
      "cluster_id": "<cluster_id>",
      "realm": "<realm>",
      "client_id": "<client_id>",
      "name": "<name>"
    },
    "name": "skycloak_create_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesdisplay name
typeNoOAuth client type: confidential or public (case-insensitive); defaults to confidential
realmYesthe realm name
protocolNoauthentication protocol: openid-connect or saml (case-insensitive); defaults to openid-connect
client_idYesthe OAuth client ID (unique within the realm)
cluster_idYesthe cluster ID
grant_typesNoenabled OAuth 2.0 grant types: authorization_code, implicit, password, client_credentials or refresh_token (case-insensitive). Defaults to authorization_code, the browser login flow. Ignored for SAML
redirect_urisNoallowed redirect URIs; required whenever authorization_code or implicit is enabled

Output Schema

NameRequiredDescriptionDefault
client_idYes
client_secretNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the mutation profile is covered. The description adds genuinely non-obvious behavior beyond that: the client secret is returned only for confidential clients and is not retrievable later, which is a critical operational caveat. It does not cover permission requirements or duplicate-handling failure modes.

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?

Two short sentences, front-loaded with the action and followed by the single most consequential return-value caveat. No filler, nothing that could be cut without losing information.

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?

An output schema exists, so return structure need not be explained, yet the description wisely calls out the one return value with lasting consequences (the secret). Remaining gap is prerequisite/error context (realm existence, duplicate client_id), which is minor for a creation tool of this complexity.

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?

Schema description coverage is 100%, so all 8 parameters (including type, protocol, grant_types and redirect_uris defaults) are already documented in the schema. The description only implicitly links the 'type' parameter to secret issuance ('for confidential clients'); baseline 3 is appropriate when the schema carries the parameter burden.

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 names a specific verb and resource ('Create an OIDC/SAML client (application)') and scopes it ('in a realm'). Against siblings like skycloak_get_application, skycloak_update_application and skycloak_delete_application, an agent can immediately tell this is the creation path without opening any schema.

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?

Usage is implied by the verb and the 'in a realm' scoping, but there is no explicit when-to-use versus alternatives, no mention of prerequisites (the realm and cluster must already exist), and no guidance on what to do if the client_id already exists. Adequate but leaves the agent to infer call conditions.

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