Skip to main content
Glama

Get cloud DNS zones

get_cloud_dns_zones
Read-only

Read the DNS zones held in the organisation's Ankra Cloud account (the twin of ankra org access-gateway zones), or with zone_id who may manage one zone's records (the twin of ankra org access-gateway get): its mode, roles, the project it is limited to and the parent zone it inherits from. Needs members.read; a caller confined to one project is refused, since the zones are the whole organisation's. Read-only; changing a policy is not offered here.

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_cloud_dns_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
zone_idNoOne zone's id, from the listing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond readOnlyHint, the description discloses the required permission, the access restriction for project-scoped callers, the switch between listing and single-zone detail, the returned fields, and that policy changes are out of scope. This is substantial behavioral context for a read tool.

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 main action and scope are front-loaded and there is little wasted text. The single long sentence and the awkward phrase 'who may manage one zone's records' make it denser and less immediately readable than it could be.

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?

For a read-only tool with no output schema, the description supplies enough context: authorization requirements, scope refusal behavior, mode switching, and the fields returned. Pagination or exact response shape is not described, but the definition is broadly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so zone_id is already documented, but the description adds important meaning: supplying it changes the operation from listing all organisation zones to returning one zone's mode, roles, project limit, and parent zone.

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 states a specific verb and resource: reading DNS zones in the organisation's Ankra Cloud account, with zone_id switching to one zone's details. It is clear, but it does not directly differentiate itself from sibling tools such as list_organisation_custom_dns_zones or list_cluster_custom_dns_zones.

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 clear usage conditions: omit zone_id to read the organisation's zones, supply zone_id to inspect one zone, members.read is required, and project-confined callers are refused. It does not name sibling alternatives, so the agent must infer when to prefer this over custom-zone listing tools.

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.