@kodim/mcp-cloudflare-dns

Get Zone Details

get_zone

Read-only

Retrieve complete configuration details for a specific DNS zone using its zone ID, including name servers, status, and account information.

Instructions

Get full details for a specific DNS zone by its zone ID. Returns zone configuration including name servers, status, and account info.

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_id": "<zone_id>"
    },
    "name": "get_zone"
  }
}

Input Schema

Name	Required	Description	Default
`zone_id`	Yes	The zone ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, and the description adds return-value context (name servers, status, account info) that is not in the schema. It does not contradict annotations and gives useful behavioral scope for a read operation.

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?

Two sentences, front-loaded with the core purpose and a brief return summary. No wasted words.

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 simple 1-parameter read tool with readOnly annotation and no output schema, the description adequately covers purpose and return contents. It could be slightly more explicit about distinguishing from list_zones, but overall it is complete for the tool's complexity.

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?

The input schema has full (100%) description coverage for zone_id, and the description uses the same term without adding format or constraints. With high schema coverage, a baseline of 3 is appropriate; the description adds no extra meaning beyond the 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?

The description clearly states the verb ('Get'), the resource ('specific DNS zone'), and the scoping ('by its zone ID'), which distinguishes it from sibling list_zones that retrieves multiple zones. It also previews returned data.

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?

The description implies use when you have a zone ID and need one zone's details, and the phrase 'specific DNS zone' contrasts with list_zones. However, it does not explicitly name alternatives or state when not to use it.

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

Deploy Server