Skip to main content
Glama
Onlydns

OnlyDNS MCP Server

Official
by Onlydns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

configure_domain_tsig

Attach a TSIG key to a domain and configure whether it permits AXFR zone transfers or RFC 2136 dynamic DNS updates.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNameYesTSIG key name
allowAxfrYesWhether to allow AXFR zone transfers for this domain using this key
domainNameYesDomain name (e.g. example.com)
allowDnsUpdateYesWhether to allow RFC 2136 DNS updates for this domain using this key

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does not say whether this grants permissions to an existing key or creates a binding, whether it overwrites prior TSIG config for the domain, whether it is idempotent, or what permissions the caller needs — all critical for a mutation tool with four required parameters.

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?

A single front-loaded sentence with zero filler; the distinguishing detail (AXFR / dynamic updates) is placed immediately after the verb.

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 four-required-parameter mutation with no annotations and no output schema, the description leaves out prerequisites, reversibility, overwrite behavior, and failure modes. It is too thin to let an agent call this safely without guessing.

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 keyName, domainName, allowAxfr and allowDnsUpdate are already documented in the schema, including the RFC 2136 reference. The description's parenthetical restates the two booleans' purpose without adding format, default, or interaction semantics.

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?

States a specific verb (attach/configure) and resource (TSIG permissions for a domain), and names the two capabilities it controls (AXFR transfers, dynamic DNS updates). This is enough to distinguish it from create_tsig_key or list_tsig_keys, though it never names its inverse sibling 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?

No when-to-use guidance, no prerequisites (a TSIG key must presumably exist first via create_tsig_key), and no mention of remove_domain_tsig as the way to undo it. The agent must infer all routing from the name alone.

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