Skip to main content
Glama

skycloak_delete_application

Destructive

Remove an OIDC/SAML application from a realm by specifying cluster ID, realm, and client ID, and set confirm=true to complete deletion.

Instructions

Delete an application (OIDC/SAML client) 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>",
      "client_id": "<client_id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe realm name
confirmYesmust be true to confirm deletion
client_idYesthe application client 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?

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds that the target is an OIDC/SAML client scoped to a realm and mentions the confirmation gate, but says nothing about permanence, cascade effects on roles/sessions, or required permissions.

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 with the action and target front-loaded and the confirmation requirement second. Nothing is superfluous and there is no filler.

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 not be described, and all parameters are documented. However, for a destructive tool the description omits whether deletion is irreversible, what dependent objects (roles, sessions, secrets) are affected, and whether elevated permissions are needed.

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 four parameters (cluster_id, realm, client_id, confirm) are already documented. The description only echoes the confirm behavior already stated in the schema and adds no format or constraint detail beyond it, making the baseline 3 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 states a specific verb ('Delete') and resource ('an application'), and clarifies the domain term with '(OIDC/SAML client) from a realm'. It does not name a sibling to differentiate from (e.g., skycloak_delete_application_role or skycloak_update_application), but the resource noun makes the target unambiguous.

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 by the operation itself; there is no explicit when-to-use versus skycloak_update_application or a note on when deletion is inappropriate. The confirm=true instruction is a useful safety gate but largely restates what the schema already enforces for the required 'confirm' parameter.

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