Skip to main content
Glama

Remove cluster custom DNS zone

remove_cluster_custom_dns_zone
Destructive

Withdraw a DNS zone a cluster declared (the twin of ankra cluster custom-dns-zones remove). Ankra removes the zone's external-dns on its next pass; the records already in the zone are left exactly as they are. An organisation-wide zone is withdrawn with ankra org custom-dns-zones remove, not here. Requires credentials.write.

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": {
      "zone": "<zone>"
    },
    "name": "remove_cluster_custom_dns_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneYesThe declared zone to withdraw.
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses that removal is deferred ('on its next pass'), that existing DNS records inside the zone survive unchanged, and that credentials.write is required. That scoping of what is and isn't destroyed is exactly the context annotations cannot convey.

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?

Four compact sentences, front-loaded with the action and resource before the behavioral caveats. The parenthetical CLI-twin reference is the one clause that adds little for an agent, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, asynchronous mutation with no output schema, the description covers the deferred execution model, record retention, auth requirement, and the alternative tool for org-scoped zones. Nothing an agent needs before invoking it is 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%, so `zone`, `cluster_id`, and `cluster_name` are already documented in the schema. The description adds no format hints or selection logic for the optional cluster identifiers, so it stays at the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('Withdraw') plus precise resource ('a DNS zone a cluster declared'), and it explicitly separates itself from the organisation-wide removal path. An agent can distinguish it from add_cluster_custom_dns_zone or list_cluster_custom_dns_zones without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear exclusion rule — an organisation-wide zone must go through `ankra org custom-dns-zones remove`, not this tool — which routes the agent correctly. It does not spell out prerequisites beyond the credentials.write note, but the when-not guidance is explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.