Skip to main content
Glama

skycloak_add_cluster_captcha_domain

Register a hostname for CAPTCHA protection on a Skycloak cluster by specifying the cluster ID and hostname, enabling bot defense for that domain.

Instructions

Register a hostname for CAPTCHA protection on a cluster.

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>"
    },
    "name": "skycloak_add_cluster_captcha_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostnameYesthe hostname to register for CAPTCHA protection
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
hostnameYes
created_atYes

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?

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the description only needs to add context — and it adds almost none. It does not say what happens when the same hostname is registered twice (relevant given idempotentHint=false), what permissions are required, or whether the registration takes effect immediately.

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?

A single front-loaded sentence with zero filler and no redundancy. It is efficient, though the brevity leaves no room for the behavioral detail an agent would need.

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?

The tool is simple (two required, fully documented parameters, an output schema, and complete annotations), so much of the burden is already carried by structured fields. Still, the description omits duplicate-registration behavior and any preconditions for a non-idempotent write, which is a meaningful gap for a mutation tool.

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%, with both 'hostname' and 'cluster_id' documented in the schema itself, so the baseline of 3 applies. The description restates the hostname purpose but adds no format constraints (wildcards, ports, scheme) or sourcing guidance for the cluster ID.

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 plus resource ('Register a hostname for CAPTCHA protection on a cluster'), which is concrete enough that an agent can tell it apart from the obvious remove/list CAPTCHA domain siblings. It stops short of naming or contrasting those siblings explicitly, so it is clear but not fully differentiated.

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?

There is no explicit when-to-use guidance, no prerequisites (e.g., whether the cluster must exist or the hostname must already be DNS-verified), and no routing to the remove/list CAPTCHA domain alternatives. Usage is only implied by the verb 'Register'.

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