Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaSourceRelated ServersScoreDiscussions
TypeScript
Hybrid

Get a zone snapshot, or list them

eurodns_dns_get_zone_snapshot
Read-onlyIdempotent

Retrieve a previous DNS zone state by snapshot ID, or list all snapshots with dates when no ID is given. Useful for inspecting pre-change records and restoring them via the save zone endpoint.

Instructions

Returns one previous state of a zone by snapshot id, or lists the zone’s snapshots with their dates when id is omitted. Use it to see what a zone held before an unintended change; to put that state back, send its records through eurodns_dns_save_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. Dates show when Glama detected each change.

  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, idempotent, non-destructive behavior. The description adds useful behavioral context about the dual mode: listing snapshots when id is omitted versus returning a specific snapshot when id is provided, plus the intended use case around rollback.

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 concise sentences, with the core behavior front-loaded and the recovery workflow in the second sentence. Every phrase earns its place and there is no redundancy.

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 simple parameter set, rich schema, annotations, and existing output schema, the description covers the essential scenarios: retrieving a snapshot and listing snapshots. It also connects the tool to the adjacent save tool, making the overall behavior complete for an agent.

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 the schema fully documents both parameters. The tool description reinforces that id is optional and its omission switches to listing mode, but it does not add substantial new parameter-level 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 identifies the action as returning a single previous zone state by snapshot id, or listing snapshots when id is omitted. It distinguishes this tool from others in the sibling list by naming the related save/restore path.

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?

The description explicitly states when to use the tool: to inspect what a zone held before an unintended change. It also gives clear guidance on the alternative path, saying to use eurodns_dns_save_zone to restore that state.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JigSawFr/eurodns-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server