Skip to main content
Glama

skycloak_list_cluster_captcha_domains

Read-only

Lists the hostnames registered for CAPTCHA protection on a specified cluster, helping you identify which domains are covered.

Instructions

List hostnames registered 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>"
    },
    "name": "skycloak_list_cluster_captcha_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
countYes
domainsYes
max_allowedYes

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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered without description support. The description does add the meaningful qualifier that results are limited to CAPTCHA-protected hostnames rather than all cluster hostnames, but it says nothing about pagination or result size, and it leaves the idempotentHint=false flag unexplained despite this being a read operation.

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?

One sentence with the scope qualifier ('CAPTCHA protection') front-loaded before the resource, and no filler. Every word constrains the result set.

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?

With one required parameter, a full output schema, and safety annotations, the description needs only to establish the resource and scope, which it does. A brief note on whether results are paginated or include wildcard/subdomains would make it fully complete.

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 coverage is 100% for the single cluster_id parameter, so the schema already carries the parameter documentation. The description only reinforces that the listing is scoped to a cluster, adding no format, source, or lookup detail 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 names a specific verb ('List') and a precisely qualified resource ('hostnames registered for CAPTCHA protection on a cluster'), so an agent knows exactly what is returned. It does not, however, contrast itself with the sibling skycloak_list_domains, leaving the boundary between general domain listing and CAPTCHA-specific domain listing to inference.

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 when-to-use or when-not-to-use guidance, and no mention of the obvious alternatives (skycloak_list_domains, skycloak_add_cluster_captcha_domain). The only usable signal is the required cluster_id, from which an agent must infer that this is a per-cluster read.

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