Skip to main content
Glama

skycloak_create_identity_provider

Create an OIDC identity provider (SSO connection) in a Skycloak realm to enable users to sign in through an external identity provider.

Instructions

Create an OIDC identity provider (SSO connection) in a realm.

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>",
      "provider_id": "<provider_id>",
      "display_name": "<display_name>"
    },
    "name": "skycloak_create_identity_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe realm name
issuerNoOIDC issuer URL
client_idNoupstream OAuth client ID
token_urlNoOIDC token endpoint
cluster_idYesthe cluster ID
provider_idYesSkycloak provider ID (case-insensitive); it becomes this provider's alias in the realm, so it must be unique there. See skycloak_list_identity_provider_templates for the accepted values
display_nameYeslogin button / display name
client_secretNoupstream OAuth client secret
authorization_urlNoOIDC authorization endpoint

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare that this mutates state, is non-idempotent, and is not destructive, so the safety profile is covered. The description adds only that the provider is an OIDC/SSO connection scoped to a realm, saying nothing about what happens on a provider_id collision (it must be unique) or whether the client_secret is echoed back.

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?

A single front-loaded sentence with the resource and scope stated immediately and no filler. It is efficient, though so terse that it reads more like a title expansion than a specification.

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?

With nine parameters, four of them required, an output schema present, and rich annotations, the structured data carries most of the burden. The description's remaining gap is workflow context: how to pick provider_id and what the caller must supply for a working OIDC connection.

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 nine parameters are already documented, including the important note that provider_id becomes the realm alias and must be unique. The description adds no parameter-level meaning beyond that baseline, so a 3 is appropriate.

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 pairs a specific verb (Create) with a specific resource (an OIDC identity provider) and states the container scope (in a realm), which is enough to distinguish it from update/delete/get identity provider siblings. It stops short of explicitly naming when a create is preferred over, say, importing a realm, so it lands just below the top.

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?

There is no when-to-use guidance, no prerequisite (such as obtaining a valid provider_id from the templates listing, which only appears inside the schema), and no exclusion of alternatives like update_identity_provider. The agent must infer the workflow entirely.

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