Skip to main content
Glama

List cluster custom DNS zones

list_cluster_custom_dns_zones
Read-only

The DNS zones one cluster serves with the organisation's own DNS credentials (the twin of ankra cluster custom-dns-zones list): its own declarations and the organisation-wide ones it inherits, each with its credential, provider (cloudflare, webhook or avura) and the external-dns policy it runs (upsert-only for Cloudflare, sync otherwise). A null provider means the credential is gone. Read-only.

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": "list_cluster_custom_dns_zones"
  }
}

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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true (restated by 'Read-only', which is redundant). Beyond that, the description discloses the returned shape: credential, provider enum values (cloudflare, webhook, avura), the external-dns policy per provider, and the important null-provider-means-credential-removed edge case. That is real behavioral context, though auth/permission requirements and pagination are unmentioned.

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?

Front-loaded with the core statement, then progressively adds scope, field inventory, and the null-provider caveat. It is one very dense sentence with stacked parentheticals and a CLI twin reference that adds little for an agent, but nearly every clause carries usable information.

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?

With no output schema, the description correctly takes on the job of explaining what each returned zone contains, including provider and policy semantics. The remaining gap is selection behavior for the optional cluster_id/cluster_name pair, which is left entirely to the schema.

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 documented, and the description adds nothing about selection precedence or what happens when neither is given. Baseline 3 applies when the schema carries the parameter burden.

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+resource ('DNS zones one cluster serves') with the scope spelled out: this cluster's own declarations plus the organisation-wide ones it inherits. That scoping sentence is what separates it from list_organisation_custom_dns_zones and from get_cluster_dns_zone, so an agent can route without opening the schema.

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?

The context of use is implied by the scoping sentence (per-cluster DNS picture including inherited zones), but there is no explicit 'use this when / use X instead' and no prerequisites. The siblings add/remove_cluster_custom_dns_zone and list_organisation_custom_dns_zones are never named, leaving the agent to infer the boundary.

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.