Skip to main content
Glama

Set DNSSEC

set_dnssec
Destructive

Turn DNSSEC on or off for a domain. Only for domains on Sitequest's nameservers (the default): Sitequest's DNS then signs the zone and the key is registered with the registry. Turn it off before set_nameservers moves the domain to another DNS provider; otherwise resolvers that validate DNSSEC stop resolving the domain until the registry drops the old key. With other nameservers, set up DNSSEC at that provider instead. Check the current state with get_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": {
      "id": "<id>",
      "enabled": "<enabled>"
    },
    "name": "set_dnssec"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID
enabledYestrue signs the zone; false turns signing off and removes the keys at the registry

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description adds substantive context beyond them: the zone gets signed and the key registered with the registry, and disabling removes keys at the registry, with a concrete failure mode (validating resolvers stop resolving until the old key is dropped).

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?

Front-loads the action, then layers scope, ordering constraint, and alternative-provider case in tight sentences with no filler.

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?

For a two-parameter mutation with no output schema, the description covers scope, side effects, ordering hazards, and the state-check path, leaving nothing an agent needs before calling it.

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 coverage is 100% and the enabled parameter already documents that true signs the zone while false removes keys at the registry, so the description adds no parameter meaning beyond the schema. Baseline 3 applies.

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 and resource ("Turn DNSSEC on or off for a domain") and immediately scopes it to domains on Sitequest's nameservers, which separates it from set_nameservers and get_domain.

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?

Gives explicit when-to-use (default nameservers), when-not (other DNS providers, where DNSSEC must be configured at that provider), and ordering guidance (turn off before set_nameservers moves the domain, check state with get_domain).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.