Skip to main content
Glama

skycloak_update_identity_provider

Idempotent

Update a Keycloak identity provider's display name and enabled state in a Skycloak cluster, letting you rename providers or toggle availability by realm and provider ID.

Instructions

Update an identity provider's display name and enabled state.

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>"
    },
    "name": "skycloak_update_identity_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
enabledNowhether the provider is enabled
cluster_idYesthe cluster ID
provider_idYesthe identity provider alias, exactly as skycloak_list_identity_providers reports it (case-sensitive)
display_nameNonew display name

Output Schema

NameRequiredDescriptionDefault
TypeYes
EnabledYes
ProviderIDYes
DisplayNameYes

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 readOnly=false, idempotent=true, destructive=false and a closed-world scope, so the safety profile is covered structurally. The description adds only the set of mutable fields; it does not say whether omitted fields are left unchanged, whether the operation validates against the provider type, or what happens on an unknown provider_id. That extra context would have earned a 4.

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 no filler or redundancy, and the mutable fields are stated up front. It is efficient but so terse that it leaves no room for the partial-update semantics an agent would want.

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 annotations covering the safety profile, an output schema covering return values, and full schema coverage on all five parameters, the structured data carries most of the burden. Still, for a mutation tool the description omits partial-update behavior and failure conditions, leaving a modest but real gap.

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 realm, cluster_id, provider_id, display_name and enabled are all documented in the schema, including the case-sensitivity note on provider_id. The description's 'display name and enabled state' merely restates two fields already described, adding no format or constraint detail beyond the schema baseline.

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?

States a specific verb (Update) and resource (identity provider) plus the two mutable fields (display name, enabled state), which clearly separates it from create/delete/get siblings. It stops short of explicitly naming an alternative, but the scope is unambiguous.

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 statement of when to use this tool versus skycloak_create_identity_provider, skycloak_get_identity_provider, or the other update_* tools, and no mention of prerequisites such as needing the provider to already exist. Usage is only implied by the word 'Update'.

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