Skip to main content
Glama

skycloak_delete_realm

Destructive

Permanently removes a realm along with all its users, clients, and configuration; requires confirm=true because deletion is irreversible.

Instructions

Permanently delete a realm and all of its users, clients and configuration. This is irreversible. 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>",
      "name": "<name>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_realm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesthe realm name to delete
confirmYesmust be true to confirm permanent, irreversible deletion of the realm and all its data
cluster_idYesthe cluster the realm belongs to

Output Schema

NameRequiredDescriptionDefault

No arguments

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 destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description nonetheless adds real value by naming exactly what is destroyed (users, clients, configuration) and flagging irreversibility plus a confirmation gate. It stops short of permission/auth requirements or what happens to dependent resources in other clusters.

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?

Three short sentences, no filler, with the irreversible consequence front-loaded ahead of the confirmation requirement. Every sentence carries distinct 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?

For a 3-parameter destructive tool with full schema coverage, an output schema, and annotations covering the safety hints, the description says enough to invoke it correctly and safely. Only edge information such as required permissions or downstream effects is absent, which is a minor 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%, and the schema already documents name, cluster_id and the confirm gate in the same terms. The description's mention of confirm=true reinforces but does not add meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ('Permanently delete a realm') and immediately bounds the blast radius ('and all of its users, clients and configuration'). That scoping distinguishes it from the sibling tools that delete a single realm sub-resource such as skycloak_delete_realm_user or skycloak_delete_realm_role.

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 only implied: the irreversibility warning signals this is a last-resort operation, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. removing individual users or clients instead). 'Set confirm=true to proceed' is a parameter constraint rather than selection guidance.

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