Skip to main content
Glama

skycloak_remove_cluster_captcha_domain

Destructive

Removes a hostname from CAPTCHA protection on a Skycloak cluster, requiring confirm=true to execute the removal.

Instructions

Remove a hostname from CAPTCHA protection on 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>",
      "hostname": "<hostname>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_remove_cluster_captcha_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesmust be true to confirm removal
hostnameYesthe hostname to remove
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 carried by structured data. The description adds the confirmation gate, which is useful context, but says nothing about consequences beyond the annotations: whether removal is reversible, whether traffic to the hostname is affected, or what the underlying tool returns on failure.

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, front-loaded with the action and followed by the one operational requirement. Nothing is padded or redundant.

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 destructive tool with a full schema, complete annotations, and an output schema, the definition covers the essential action and the confirmation gate. What it omits (reversibility, post-removal behavior) is minor given that annotations already flag the destructive nature.

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 in-schema, including 'confirm must be true to confirm removal.' The description only restates the confirm requirement, adding no new semantics for hostname or cluster_id, so this sits at the baseline for a fully documented 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 opens with a specific verb and resource: 'Remove a hostname from CAPTCHA protection on a cluster.' That is unambiguous and clearly distinct from the sibling add/list CAPTCHA-domain tools, though the description never names those alternatives explicitly, which keeps it 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?

Usage is implied by the narrow scope (removing a hostname from CAPTCHA protection), and the 'Set confirm=true to proceed' line signals a deliberate two-step intent. However, there is no guidance on when to prefer this over alternatives, no prerequisites (permissions, cluster state), and no note on when not to use it.

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