Skip to main content
Glama
Sign In
OnlyDNS MCP Server

OnlyDNS MCP Server

Official
by Onlydns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

configure_domain_tsig

Attach and configure TSIG key permissions for a domain, enabling AXFR zone transfers and RFC 2136 dynamic DNS updates with optional subdomain restrictions.

Instructions

Attach and configure TSIG permissions (AXFR transfer / dynamic DNS updates / subdomain restrictions) for a domain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domainName": "<domainName>",
      "keyName": "<keyName>",
      "allowAxfr": "<allowAxfr>",
      "allowDnsUpdate": "<allowDnsUpdate>"
    },
    "name": "configure_domain_tsig"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNameYesTSIG key name
allowAxfrYesWhether to allow AXFR zone transfers for this domain using this key
domainNameYesDomain name (e.g. example.com)
subdomainsNoOptional list of allowed subdomains (e.g. ["_acme_challenge"]). If specified, dynamic DNS updates are restricted to these subdomains.
allowDnsUpdateYesWhether to allow RFC 2136 DNS updates for this domain using this key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.5
    • addedInput schema / properties / subdomains
      Added value: +{
+  "description": "Optional list of allowed subdomains (e.g. [\"_acme_challenge\"]). If specified, dynamic DNS updates are restricted to these subdomains.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed3 schema fields changed
    • removedInput schema / properties / key
      Removed value: -{
-  "description": "TSIG key name",
-  "type": "string"
-}
    • addedInput schema / properties / keyName
      Added value: +{
+  "description": "TSIG key name",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "domainName",
-  "key",
-  "allowAxfr",
-  "allowDnsUpdate"
-]New value: +[
+  "domainName",
+  "keyName",
+  "allowAxfr",
+  "allowDnsUpdate"
+]
  3. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a mutation operation. It states what permissions can be configured but omits whether existing TSIG configuration is overwritten, what permissions or authentication are required, whether the operation is idempotent, and what happens when subdomains is omitted.

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 a single, front-loaded sentence with no filler. The key operation and the permission categories are presented immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is too thin. It does not explain authorization requirements, overwrite/merge behavior, or the effect of omitting optional parameters, leaving important operational context unaddressed despite the schema's complete parameter documentation.

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 all five parameters are already documented in the input schema. The description adds a high-level mapping of the permission types but does not add syntax, defaults, or edge-case semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource combination ('Attach and configure TSIG permissions') and enumerates the permission types it handles (AXFR, dynamic updates, subdomain restrictions). It is clear enough to distinguish from retrieval/removal siblings, though it does not explicitly name when to choose this over create_tsig_key or remove_domain_tsig.

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

Usage Guidelines2/5

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

The description offers no explicit when-to-use guidance, prerequisites, or alternatives. It does not clarify whether this is for new TSIG attachment versus modifying existing permissions, nor does it reference related tools such as create_tsig_key or get_domain_tsig.

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