SatsDNS

DNSSEC DS record for the registrar (free, token)

dnssec_info

Read-onlyIdempotent

Free: the DS record(s) to enter at the registrar, and what the parent zone publishes now. Pass the zone token (jdz_...) from the create answer, or a scoped account API key (jdk_...) made in the dashboard. Either passes through your model context and transcript: treat it like a password.

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": {
      "zone": "<zone>"
    },
    "name": "dnssec_info"
  }
}

Input Schema

Name	Required	Description
`zone`	Yes	The hosted zone, e.g. example.com.
`token`	No	The zone token (jdz_...); or give api_key.
`api_key`	No	Instead of token: an account API key (jdk_...) whose scope covers this object (read, or write for changes).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, and the description adds genuinely new context: the credential passes through the model context and transcript and should be treated like a password. That security disclosure is not derivable from structured fields. It does not describe rate limits or output shape, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with no filler, and the returned-value statement is front-loaded before the credential instructions. The leading 'Free:' fragment is slightly awkward but does not waste space.

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?

With three fully documented parameters, no output schema, and annotations covering the safety profile, the description supplies the missing pieces: what the result represents and how to authenticate. It omits any note on error behavior when DNSSEC is unconfigured, which keeps it from a 5.

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%, so the baseline is 3; the description largely mirrors the schema's own explanation of token and api_key. The only added nuance is that the zone token comes 'from the create answer,' which is marginally useful but not substantive.

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 names a specific resource and deliverable: the DS record(s) for the registrar plus what the parent zone currently publishes. An agent can tell this is a DNSSEC-record retrieval step, and no sibling tool covers DNSSEC, but the description never states the verb explicitly or distinguishes itself from siblings like info or zone_status.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the token is said to come 'from the create answer,' which suggests this runs after zone creation, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling tools.

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

All SatsDNS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?