Skip to main content
Glama

skycloak_verify_domain

Idempotent

Triggers DNS verification for a custom domain in a Skycloak cluster and returns its updated verification status.

Instructions

Trigger DNS verification for a custom domain and return its updated status.

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

Input Schema

NameRequiredDescriptionDefault
domain_idYesthe domain ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
idYes
domainYes
is_activeYes
subdomainNo
ssl_statusNo
dns_recordsNo
cname_targetNo
verification_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety and repeatability profile is covered. The description adds that the call returns the updated status, which is useful, but says nothing about asynchronous behavior, propagation delays, authorization requirements, or what happens if verification is already complete.

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 compact sentence with the action and outcome front-loaded and no filler wording. It could be slightly stronger by leading with the prerequisite or expected result, but nothing is wasted.

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?

The tool is low complexity with two fully documented parameters, an output schema covering return values, and annotations covering the safety profile. The description is therefore close to sufficient, with only prerequisite and async guidance missing.

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 two required parameters (cluster_id, domain_id) already documented in the input schema. The description adds no syntax, format, or relationship detail beyond the schema, so the baseline of 3 is appropriate.

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 ('Trigger') and resource ('DNS verification for a custom domain') and states the outcome ('return its updated status'), which is enough to distinguish it from sibling CRUD tools like create_domain or get_domain. It stops short of explicitly naming the siblings it is not, so it falls just below the top band.

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, no stated prerequisites (e.g. domain already created, DNS records configured), and no reference to alternatives such as get_domain for status checks. The only cue is the implied notion that this is used on an existing custom domain.

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