Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a zone snapshot, or list them

eurodns_dns_get_zone_snapshot
Read-onlyIdempotent

Retrieve a previous DNS zone snapshot by ID to inspect records before an unintended change, or list available snapshots with dates when no ID is provided.

Instructions

Returns one earlier state of the zone domainName by snapshot id — its records as they were — or lists the zone’s snapshots with their ids and dates when id is omitted. Use it to see what a zone held before an unintended change; it reads only and restores nothing. To put a state back, send its records through eurodns_dns_save_zone, or one record at a time through eurodns_dns_upsert_record rather than replacing the zone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric id of the snapshot to return. Omit it to list the snapshots of the zone, with their ids and dates.
domainNameYesName of the zone, e.g. example.com: a domain whose DNS is hosted here.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResponse body as returned by the API.
statusYesUpstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.10.0
    • 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."
    • changedInput schema / properties / id / description
      Previous value: -"id of Zone Snapshot to return"New value: +"Numeric id of the snapshot to return. Omit it to list the snapshots of the zone, with their ids and dates."
    • changedInput schema / required
      Previous value: -[
-  "domainName",
-  "id"
-]New value: +[
+  "domainName"
+]
  2. First observedv0.9.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only, but the description adds nuance: it clarifies that omitting id lists snapshots, and it warns against replacing the zone, enriching behavioral context beyond the annotations.

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 two sentences, front-loaded with the primary action, and avoids redundancy. It efficiently packs purpose and usage guidance without unnecessary detail.

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?

Given the tool's simple two-parameter interface and the presence of an output schema, the description covers all necessary behavioral aspects, including the optional id behavior and relationship to other DNS operations.

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 descriptions fully cover both parameters (domainName and id) with adequate detail. The tool description repeats similar information without adding new meaning, so it adds little 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 tool returns a snapshot or lists snapshots for a zone, with the verb 'Returns' and 'lists'. It distinguishes from siblings by emphasizing read-only behavior and contrasts with restore operations.

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?

It explicitly instructs to use this tool for viewing historical zone states and points to save_zone or upsert_record for restoring, providing clear when-to-use and when-not-to-use guidance.

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

Deploy Server

Other Tools