Skip to main content
Glama
Sign In
dynadot-mcp

dynadot-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_dnssec

Configure DNSSEC for a domain by setting DS records or DNSKEYs, or clear it to disable validation. Supports key tags, digests, algorithms, and flags.

Instructions

Set or clear DNSSEC for a domain. Provide either a DS record (key_tag, digest_type, digest, algorithm) or a DNSKEY (flags, public_key, algorithm). To disable, set clear to true without key fields.

Input Schema

NameRequiredDescriptionDefault
clearNoSet to true to remove DNSSEC from the domain
flagsNoDNSSEC flags (e.g., '257' for KSK)
digestNoDS digest in hexadecimal
domainYesDomain name to configure DNSSEC for
key_tagNoDS key tag (0-65535)
algorithmNoDNSSEC algorithm number (e.g., '13' for ECDSAP256SHA256)
public_keyNoDNSSEC public key
digest_typeNoDS digest type: 1=SHA-1, 2=SHA-256, 3=GOST, 4=SHA-384

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.2
    • addedInput schema / properties / algorithm / enum
      Added value: +[
+  "1",
+  "2",
+  "3",
+  "4",
+  "5",
+  "6",
+  "7",
+  "8",
+  "10",
+  "12",
+  "13",
+  "14",
+  "15",
+  "16",
+  "252",
+  "253",
+  "254"
+]
    • addedInput schema / properties / digest
      Added value: +{
+  "description": "DS digest in hexadecimal",
+  "pattern": "^[0-9a-fA-F]+$",
+  "type": "string"
+}
    • addedInput schema / properties / digest_type
      Added value: +{
+  "description": "DS digest type: 1=SHA-1, 2=SHA-256, 3=GOST, 4=SHA-384",
+  "enum": [
+    "1",
+    "2",
+    "3",
+    "4"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / flags / enum
      Added value: +[
+  "256",
+  "257"
+]
    • addedInput schema / properties / key_tag
      Added value: +{
+  "description": "DS key tag (0-65535)",
+  "pattern": "^\\d+$",
+  "type": "string"
+}
    • addedInput schema / properties / public_key / minLength
      Added value: +1
    • addedInput schema / properties / public_key / pattern
      Added value: +"^[A-Za-z0-9+/]+={0,2}$"
  2. First observedv1.3.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the destructive path ('set clear to true without key fields') and the mutually exclusive input modes, but says nothing about required permissions, propagation delay, whether an existing DNSSEC config is overwritten, or error behavior.

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?

Three sentences, zero filler, with the core operation front-loaded before the mode-selection detail. Each sentence earns its place by adding a distinct piece of operational information.

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 an 8-parameter mutation tool with no output schema and no annotations, the description covers the essential selection logic between input modes. It is slightly incomplete on permissions, overwrite semantics, and failure modes, but the functional picture needed to call it correctly is present.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning the schema does not express: it groups key_tag/digest_type/digest/algorithm as one DS-record option and flags/public_key/algorithm as a separate DNSKEY option, implying mutual exclusivity that the flat schema leaves ambiguous.

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?

States a specific verb pair (set/clear) and resource (DNSSEC for a domain), which is unambiguously distinct from the read-only sibling get_dnssec and from generic domain tools like set_dns. An agent can identify the operation without opening the schema.

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 gives concrete invocation context by laying out three mutually exclusive modes: a DS record, a DNSKEY, or clear=true. It does not state prerequisites (e.g. domain must already be registered) or exclusions, so it stops short of full when/when-not 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