Skip to main content
Glama

skycloak_delete_smtp

Destructive

Removes a Keycloak realm's SMTP configuration from a Skycloak cluster; set confirm=true to proceed.

Instructions

Remove a realm's SMTP configuration. 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>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_smtp"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
confirmYesmust be true to confirm deletion
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the danger profile is known. The description adds the confirm-gate requirement, which is real value, but says nothing about consequences (SMTP delivery ceasing), whether the realm itself is affected, or the response shape despite an output schema existing.

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, zero redundancy, and the destructive condition is front-loaded. Nothing could be removed without losing 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 simple three-parameter delete with strong annotations and an output schema, the definition covers what and how. Only the aftermath of deletion is unstated, a minor gap given the annotation coverage.

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 each parameter is already documented, so the schema does the heavy lifting. The description only repeats the confirm flag and adds no meaning about realm or cluster_id semantics 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 gives a specific verb+resource ("Remove a realm's SMTP configuration"), so its effect is unmistakable. It does not name or distinguish itself from siblings such as skycloak_upsert_smtp or skycloak_get_smtp, leaving that differentiation to the names alone.

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?

"Set confirm=true to proceed" is a parameter instruction, not usage guidance. Nothing states when to use this versus modifying SMTP via upsert, or whether the current config should be inspected first.

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