Skip to main content
Glama

skycloak_create_domain

Adds a custom domain to a cluster and returns the DNS records required to verify and route it.

Instructions

Add a custom domain to a cluster. Returns the DNS records the customer must create to verify and route the domain.

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

Input Schema

NameRequiredDescriptionDefault
domainYesthe fully-qualified domain name
subdomainNooptional subdomain
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.4/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the bar is lower. The description does add valuable context beyond them: the call produces actionable DNS records the customer must create to verify and route the domain, which implies the domain is left in a pending state. It stops short of saying the domain stays unverified until a separate verification call, or whether re-calling with the same domain is safe.

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 sentences, zero filler, with the action front-loaded and the return-value consequence second. Nothing needs trimming and no sentence is 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?

An output schema exists and the description correctly defers return-value details while flagging the one thing an agent must act on (DNS records to create). What is missing is the workflow link to skycloak_verify_domain and the resulting pending domain state, which matters for an agent orchestrating the full setup.

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%, so all three parameters (cluster_id, domain, subdomain) are already documented in the schema. The description adds no semantics beyond that — notably it never mentions the optional subdomain or the expected domain format handling. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ("Add a custom domain to a cluster") plus the immediate outcome (returns DNS records). It does not differentiate itself from near-siblings such as skycloak_create_domain_route or skycloak_add_cluster_captcha_domain, so the agent must infer which domain-creating tool applies.

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?

No statement of when to use this versus the sibling domain tools, no prerequisites (e.g. cluster must exist/is active), and no follow-up pointer to skycloak_verify_domain. The only usage signal is the implied "returns DNS records"; all routing decisions are left to inference.

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