Skip to main content
Glama
Sign In

SatsDNS

by com.satsdns
OverviewDiscussionsAdmin

Zone status (free, token)

zone_status
Read-onlyIdempotent

Free: state, expiry, nameservers, delegation and usage of a hosted zone. 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": "zone_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneYesThe hosted zone, e.g. example.com.
tokenNoThe zone token (jdz_...); or give api_key.
api_keyNoInstead 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.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive, so the description focuses on what annotations cannot express: the two credential paths (jdz_ zone token vs jdk_ scoped account key) and a concrete warning that the credential passes through model context and should be treated like a password. It does not mention rate limits or freshness of the reported state.

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?

What is returned is front-loaded in the first clause, followed by the credential guidance, with no filler. The sentence is dense but each part carries information.

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 no output schema, the description correctly enumerates the returned fields, and it explains the authentication model an agent needs before calling. Remaining gaps are minor: no note on what 'usage' comprises, on delegation meaning, or on failure modes for an invalid/expired token.

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 schema already documents zone, token and api_key including the jdz_/jdk_ prefixes. The description adds only marginal provenance ('from the create answer', 'made in the dashboard'), so baseline 3 applies.

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 (a hosted zone) and enumerates exactly what is returned: state, expiry, nameservers, delegation and usage. It implicitly contrasts with mutating siblings like zone_create/records_change, though it never names hostname_status or account_objects, which an agent might confuse it with.

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 only implied: the mention of the token 'from the create answer' hints this is the follow-up to zone_create. There is no explicit statement of when to prefer this over info, hostname_status, or check, and no exclusions.

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