Skip to main content
Glama

skycloak_delete_identity_provider

Destructive

Deletes an identity provider from a realm, requiring confirm=true to proceed. Use it to remove a specific provider alias from a cluster's realm.

Instructions

Delete an identity provider from a realm. Set confirm=true to proceed.

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

Input Schema

NameRequiredDescriptionDefault
realmYesthe realm name
confirmYesmust be true to confirm deletion
cluster_idYesthe cluster ID
provider_idYesthe identity provider alias to delete, exactly as skycloak_list_identity_providers reports it (case-sensitive)

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 destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is supplied structurally. The description reinforces the confirmation gate, which is useful but duplicates the required confirm parameter described in the schema, and says nothing about irreversibility or what happens to users or applications bound to the provider.

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?

Two short sentences, front-loaded with the destructive action and followed by the gate condition; nothing is buried. The second sentence is mildly redundant against the required confirm field but is cheap and arguably helpful for a destructive call.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. However, for a destructive delete the description leaves out consequences (cascading removal of linked users/role mappings, whether the action is reversible), which is the main gap an agent would care about.

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%, including a notably explicit note that provider_id is the case-sensitive alias as reported by skycloak_list_identity_providers. The description adds no parameter meaning beyond restating confirm=true, so the baseline 3 applies.

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 states a specific verb and resource ('Delete an identity provider') and scopes it to a realm, which clearly separates it from create/get/update/list siblings in the same family. It stops short of any explicit differentiation from those siblings, but the resource name carries the distinction.

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 guidance on when to choose this over alternatives such as update (e.g., disabling rather than removing) or when it is unsafe/invalid. The only usage instruction is 'Set confirm=true to proceed', which is a call-shape reminder the schema already enforces via a required field.

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