Skip to main content
Glama
Sign In

SatsDNS

by com.satsdns
OverviewDiscussionsAdmin

Expiry reminders for a dynamic hostname by Nostr DM (free, token)

hostname_reminders
Idempotent

Free: sets the Nostr key (npub) that gets direct-message reminders 14, 7 and 1 days before the hostname expires, when grace starts and before removal, or removes it with clear=true. The key gets reminders only, no control. A hostname owned by an account keeps its reminders at the account (account_reminders). Pass the hostname token (jdh_...) 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": {
      "hostname": "<hostname>"
    },
    "name": "hostname_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
npubNoThe Nostr public key (npub1... or 64 hex) that gets direct-message reminders before the hostname expires. Reminders only: it gets no control.
clearNotrue removes the reminder key instead (give no npub then).
tokenNoThe hostname token (jdh_...); or give api_key.
api_keyNoInstead of token: an account API key (jdk_...) whose scope covers this object (read, or write for changes).
hostnameYesThe hostname, e.g. myhome.dynkite.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which only say idempotent, non-destructive, open-world), the description discloses the exact reminder cadence (14, 7, 1 days, grace start, pre-removal), that the key receives reminders only and no control, and a credential-handling warning that the token passes through model context and transcripts. These are substantive behavioral facts an agent could not infer from the structured fields.

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 dense and front-loads the primary action and the free-tier signal before credential details. Some phrasing is run-on ('when grace starts and before removal') and the alternative-tool note is tucked mid-paragraph, but there is little outright waste.

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?

For a 5-parameter, 100%-covered schema with annotations but no output schema, the description covers action, timing, auth paths, sibling routing, and credential risk. It does not say what a successful call returns or whether setting a new npub replaces an existing one, which would complete the picture.

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 the schema already documents npub format, clear semantics, jdh_/jdk_ token types, and the hostname example. The description largely restates that (reminder key, clear=true, token-or-API-key) rather than adding syntax or interaction rules; the one genuinely additive note is the password-like handling of credentials.

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?

The description names a specific verb and resource (sets/removes the Nostr npub that receives expiry reminders for a hostname) and enumerates the reminder schedule and the clear=true removal path. It also distinguishes the account-owned case by pointing at account_reminders, so an agent can tell this apart from the broader account tooling.

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

Usage Guidelines4/5

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

It gives clear context for use (free tier, reminders-only key, no control granted) and routes account-owned hostnames to account_reminders, plus states the two credential forms accepted. It does not explicitly frame a when-not-to-use case beyond that routing hint, so it falls short of a full 5.

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

All SatsDNS toolsInspect
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