Skip to main content
Glama

skycloak_get_domain

Read-only

Retrieves a custom domain by cluster and domain ID, returning its DNS records plus verification and SSL status so you can inspect and troubleshoot domain configuration.

Instructions

Get a custom domain by ID, including its DNS records and verification/SSL 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_get_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.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. The description adds useful behavioral detail by stating that DNS records and verification/SSL status are included in the response, which tells the agent this is a richer read than a bare lookup. It says nothing about error behavior for an unverified or missing domain, and the idempotentHint=false annotation goes unexplained.

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, zero waste, with the resource and the returned payload front-loaded. Nothing is padded or repeated from the schema.

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?

This is a simple two-parameter read with an output schema, so return-value explanation is unnecessary and the description correctly stays brief while noting the notable response contents. The only real gap is the absence of routing guidance against sibling domain tools, which matters given how many domain-related siblings exist.

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%, so both cluster_id and domain_id are already documented in the schema. The description adds only the generic notion of lookup "by ID" and no format, scope, or relationship detail beyond what the schema provides; baseline 3 applies.

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 gives a specific verb and resource ("Get a custom domain by ID") and names the payload contents (DNS records, verification/SSL status). It does not distinguish itself from nearby siblings such as skycloak_get_domain_route or skycloak_list_domain_routes, so an agent must infer the boundary from names alone.

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 statement, no prerequisites, and no mention of alternatives like verify_domain or get_domain_route. The phrase "by ID" only weakly implies the lookup pattern (obtain an ID elsewhere, then fetch details), leaving the agent to infer the calling context.

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