Skip to main content
Glama

Get cluster DNS zone

get_cluster_dns_zone
Read-only

The cluster's generated DNS zone and public domain (the twin of ankra cluster domain): the ankra.cc zone name, its state, whether the cluster opted out, and the public_domain hostnames on the cluster are published under - the organisation's own domain when a DNS controller publishes it, otherwise the generated zone. Read-only; enabling or disabling the generated zone is a portal decision.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cluster_dns_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.7/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes the safety profile, and the description goes beyond it by stating that the operation is read-only and that zone enable/disable is not actionable here but a portal decision. It also explains the fallback logic (org domain when a DNS controller publishes it, otherwise the generated zone), which is genuine behavioral context an annotation could not carry.

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?

The core payload (what this returns) is front-loaded in a single dense sentence, and the operational caveat is a short second sentence. The main clause is heavily nested with parentheticals and dashes, which costs some readability, but nothing is padding.

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?

There is no output schema, and the description compensates by enumerating the returned fields and the rule governing which domain is reported. For a simple two-optional-parameter read tool, that is essentially everything an agent needs before calling it.

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 cluster_id and cluster_name are already fully documented, including the 'optional when a cluster is selected' fallback. The description adds nothing about either parameter, so the baseline 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 the specific resource (the cluster's generated DNS zone) and enumerates exactly what is returned: the ankra.cc zone name, its state, the opt-out flag, and the public_domain hostnames. The word 'generated' implicitly contrasts with the custom-zone siblings (list_cluster_custom_dns_zones, add_cluster_custom_dns_zone), but no sibling is named, so the differentiation must be inferred.

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

Usage Guidelines3/5

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

Usage is implied by the content description: an agent reads this to learn which domain the cluster's workloads publish under. The closing clause ('enabling or disabling the generated zone is a portal decision') usefully rules out a mutation path, but no alternative tool is named for the related custom-zone lookups, leaving routing to inference.

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.