eurodns-mcp

Get a DNS zone

eurodns_dns_get_zone

Read-onlyIdempotent

Retrieve the complete DNS zone for a domain, listing every record with ID, type, host, data, and TTL, plus URL and mail forwards, enabling inspection before changes.

Instructions

Returns the live zone of domainName in full: every DNS record with its id, type, host, rdata and ttl, plus the URL forwards and mail forwards. Read it before any change, and to find the recordId that eurodns_dns_delete_record takes. To change one record use eurodns_dns_upsert_record rather than editing this document and saving it back with eurodns_dns_save_zone, which replaces the whole zone. A domain whose DNS is not hosted here answers 404.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domainName`	Yes	Name of the zone, e.g. example.com: a domain whose DNS is hosted here.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Response body as returned by the API.
`status`	Yes	Upstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.0Sep 7, 2026

changedInput schema / properties / domainName / description

Previous value: -"a domain name (e.g. example.com)"New value: +"Name of the zone, e.g. example.com: a domain whose DNS is hosted here."

First observedv0.9.1Sep 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses that the zone is 'live' (not a snapshot), specifies the 404 error condition, and lists exactly what data is returned, adding behavioral detail.

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?

The description is informative without being bloated. It front-loads the core purpose, then provides actionable usage guidance and contrasts with related tools, all in a well-organized structure.

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 simple get operation, the description covers the purpose, expected inputs, error cases, and relationship to sibling tools. It also enumerates the returned data fields, making it self-contained for an agent.

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?

The schema covers the single parameter with 100% coverage, and the description enhances it with an example and clarifies that the domain must be hosted by this service. This adds semantic value beyond the bare 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?

Clearly states that the tool returns the full live DNS zone for a domain, listing record fields and additional data like URL and mail forwards. This distinguishes it from other operations like save or upsert.

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

Usage Guidelines5/5

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

Explicitly advises reading the zone before any change, for finding record IDs for deletion, and contrasts with upsert for single-record changes and save_zone for full-zone replacement. Also notes the 404 case for unhosted domains.

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

Deploy Server