Skip to main content
Glama

skycloak_delete_domain_route

Destructive

Deletes a realm route from a custom domain; set confirm=true to proceed when removing unused routing.

Instructions

Remove a realm route from a custom domain. 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>",
      "route_id": "<route_id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_domain_route"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 nothing beyond that: it does not say whether the removed route is recoverable, what happens to traffic previously routed through it, or whether the domain itself is affected. The confirm sentence merely restates the schema's required parameter.

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 sentences, front-loaded with the action and scoped to the domain, with no filler. The brevity borders on under-specification for a destructive operation, but nothing is redundant or padded.

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 explained, and annotations cover the destructive character. However, for an irreversible four-parameter delete the description omits any note on consequences (traffic loss, route irrecoverability), which an agent needs before confirming deletion.

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, domain_id, route_id, confirm) are already documented in the schema. The description adds no format hints, lookup guidance, or relationships between cluster/domain/route identifiers, 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 names a specific verb and resource: 'Remove a realm route from a custom domain.' This clearly separates it from the create/get/update/list domain-route siblings by its destructive action. It does not explicitly name an alternative, but the operation is unambiguous.

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 invocation mechanics rather than when-to-use guidance; the schema already marks confirm as required. There is no statement of when this tool is appropriate versus skycloak_update_domain_route (which could repoint a route) or when deletion should be avoided.

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