SatsDNS

Lightning address that renews a zone or hostname (free, token)

renewal_address

Idempotent

Free: the Lightning address and LNURL that extend this zone or hostname pro rata when anyone pays it (no token needed to pay). Made once, then the same address is returned. 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": {
      "kind": "<kind>",
      "name": "<name>"
    },
    "name": "renewal_address"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	Zone or dynamic hostname.
`name`	Yes	The zone or hostname.
`token`	No	Its token (jdz_... or jdh_...); 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.8/5.0

Behavior4/5

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

The description adds meaningful behavior beyond the annotations: it states the service is free, that no token is needed to pay, that the address is created once and then reused (idempotent), and it warns that the token/API key is sensitive and passes through model context. It does not cover error cases or rate limits, but with annotations already declaring idempotency and safety, this is strong added context.

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?

The description is three tight sentences that front-load the core purpose, then explain credential options, and end with a security warning. It is dense but not bloated; every sentence contributes useful information, though the phrasing around context/transcript is slightly awkward.

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?

There is no output schema, so the description carries the burden of explaining the return value, and it does describe that the tool returns a Lightning address and LNURL, with the same address returned on repeat calls. It also covers authentication options and security handling, leaving only minor gaps such as error behavior and response shape.

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 parameter fields are already well documented. The description adds useful semantics beyond the schema by specifying where the token comes from (the create answer) and that the API key is scoped and dashboard-created, plus a security warning about treating the token like a password.

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 clearly states that the tool returns a Lightning address/LNURL that extends a zone or hostname pro rata when paid, which is a specific and understandable action. It implicitly distinguishes itself from a direct renewal sibling by focusing on a persistent payment address, but it never names or contrasts with the sibling `renew` tool, so this is not a 5.

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?

The description explains the use case (get a shareable Lightning address that anyone can pay to renew the zone/hostname pro rata) and notes that the same address is returned after the first call. However, it does not explicitly say when to use this tool versus a direct renewal tool like `renew`, nor does it provide any exclusions or alternative-selection guidance.

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?