Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Enable or disable DNSSEC, at the registry or on the zone

eurodns_domain_set_dnssec

Enable or disable DNSSEC for a domain. Use registry scope to sign and publish DS records, or zone scope to sign only. Check status before and after to avoid broken validation.

Instructions

Enables (enabled: true) or disables (enabled: false) DNSSEC for a domain and returns nothing on success. Use scope registry for a domain registered in this account: it signs the hosted zone and publishes the DS records at the registry in one step. Use scope zone only for a domain registered elsewhere whose DNS is hosted here, then publish the DS data at that registrar yourself. Disabling one side while the other stays signed breaks validation until caches expire, so read eurodns_dns_get_dnssec_status before and after; the call does not check that state for you.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeYesregistry publishes or withdraws the DS records of a domain registered here; zone starts or stops signing a zone hosted here, for a domain registered elsewhere.
enabledYestrue to enable DNSSEC in that scope, false to disable it.
domainNameYesFully qualified domain name, e.g. example.com, as listed by eurodns_domain_get when called without a domainName.

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. Changed4 schema fields changedv0.11.0
    • changedInput schema / properties / domainName / description
      Previous value: -"Fully qualified domain name, e.g. example.com, as listed by eurodns_domain_search."New value: +"Fully qualified domain name, e.g. example.com, as listed by eurodns_domain_get when called without a domainName."
    • changedInput schema / properties / enabled / description
      Previous value: -"true to publish the DS records at the registry, false to withdraw them."New value: +"true to enable DNSSEC in that scope, false to disable it."
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "registry publishes or withdraws the DS records of a domain registered here; zone starts or stops signing a zone hosted here, for a domain registered elsewhere.",
+  "enum": [
+    "registry",
+    "zone"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "domainName",
-  "enabled"
-]New value: +[
+  "domainName",
+  "scope",
+  "enabled"
+]
  2. Addedv0.10.0

TDQS

A5/5.0
Behavior5/5

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

The description discloses side effects: signing the zone, publishing DS records, and the risk of breaking validation if only one side is disabled. It also states that the call returns nothing, complementing annotations that indicate this is a non-read-only, non-idempotent, non-destructive 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?

The description is information-dense without being verbose. It packs scope distinction, prerequisites, side effects, and a warning into a few sentences, each earning its place.

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?

The description fully explains the operation, when to use each scope, what changes occur, what to check before and after, and the return behavior. This is complete for an agent to decide when and how to call it safely.

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

Parameters5/5

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

The schema already covers all parameters at 100%, and the description adds meaningful context for each: scope clarifies registry vs. zone behavior, enabled clarifies true/false meaning, and domainName specifies fully qualified format and how to find the value via eurodns_domain_get.

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 enables or disables DNSSEC for a domain in one of two scopes, with a specific verb and resource. It distinguishes itself from sibling tools by focusing on setting DNSSEC state rather than checking or managing 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 Guidelines5/5

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

It explicitly explains when to use registry scope versus zone scope, including the prerequisite of the domain being registered elsewhere for zone scope. It also advises checking eurodns_dns_get_dnssec_status before and after, which is directly relevant sibling tool usage.

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