Skip to main content
Glama

skycloak_delete_domain

Destructive

Remove a custom domain from a Skycloak cluster by specifying the cluster and domain IDs, with a required confirmation flag to proceed with deletion.

Instructions

Remove a custom domain from a cluster. 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>",
      "domain_id": "<domain_id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesmust be true to confirm deletion
domain_idYesthe domain ID to delete
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is known. The description adds the confirm=true guard, but the schema already documents that parameter. The description does not say whether deletion is permanent, or what happens to attached domain routes or verification state.

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 are front-loaded with the action and the safety gate. There is no wasted wording.

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 and the annotations cover destructiveness, so the description does not need to cover return values. For a destructive, non-idempotent delete, however, it should state irreversibility and any side effects on related routes.

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 all three parameters are documented inline, so the baseline is 3. The description restates the confirm gate and implies domain_id belongs to a cluster, but it adds no new meaning beyond the schema.

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 uses a specific verb and resource: 'Remove a custom domain from a cluster.' That clearly separates it from create_domain, get_domain, and list_domain_routes. It does not explicitly distinguish it from the close sibling skycloak_delete_domain_route, so it falls short of a 5.

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?

The description says nothing about when to use this tool instead of alternatives, such as delete_domain_route or remove_cluster_captcha_domain, and it does not list prerequisites. Usage is only implied by the name and the purpose sentence.

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