Skip to main content
Glama

isitdns

by net.isitdns
OverviewDiscussionsAdmin

Read a registration

registration
Read-onlyIdempotent

Read a domain's registration from its registry's RDAP server: each status with what it means for resolution, the registration, expiry and change dates, the nameservers, whether the delegation is signed. Not for what DNS answers: check_domain. Read over HTTPS from the isitdns edge through IANA's RDAP bootstrap, and no contacts are returned. A hostname is read at the name, then each parent down to the registered domain, and each HTTP read is listed with its URL, status and time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain or a hostname under it. Also as "name"; a URL is read as its host.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiYesThe /api GET that asks it again, as a new reading
readsYesEach HTTP read: url, at, ms, status, error
domainYesThe registered domain answered for
eventsNoDates by event: registration, expiration, last changed
readAtYesWhen the lookup began
statusYesEach status, its effect, what it means for resolution
nameserversNoThe nameservers on file, null if the registry sent none
delegationSignedNoDS at the registry, null if not stated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "api": {
+      "description": "The /api GET that asks it again, as a new reading",
+      "type": "string"
+    },
+    "delegationSigned": {
+      "description": "DS at the registry, null if not stated",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "domain": {
+      "description": "The registered domain answered for",
+      "type": "string"
+    },
+    "events": {
+      "description": "Dates by event: registration, expiration, last changed",
+      "type": "object"
+    },
+    "nameservers": {
+      "description": "The nameservers on file, null if the registry sent none",
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "readAt": {
+      "description": "When the lookup began",
+      "type": "string"
+    },
+    "reads": {
+      "description": "Each HTTP read: url, at, ms, status, error",
+      "type": "array"
+    },
+    "status": {
+      "description": "Each status, its effect, what it means for resolution",
+      "type": "array"
+    }
+  },
+  "required": [
+    "domain",
+    "status",
+    "reads",
+    "readAt",
+    "api"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"The registered domain or a hostname under it, e.g. example.com. Also accepted as \"name\"; a URL is reduced to its host."New value: +"The domain or a hostname under it. Also as \"name\"; a URL is read as its host."
  3. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"The registered domain or a hostname under it, e.g. example.com"New value: +"The registered domain or a hostname under it, e.g. example.com. Also accepted as \"name\"; a URL is reduced to its host."
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly/openWorld/idempotent/non-destructive), the description adds substantial context: no contacts are returned, reads traverse the hostname up through each parent to the registered domain, and each HTTP read is reported with URL, status and time. These are behavioral traits the structured fields do not convey.

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?

Front-loaded with the core action and resource, and every clause carries information about output or traversal. Some sentences are dense and comma-heavy, which slightly hurts scannability, but there is 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?

Annotations cover the safety profile and an output schema exists, so return values need not be described — yet the description still characterizes them. Nothing needed to select or invoke this single-parameter tool is missing.

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% and already documents that a URL is read as its host, so the baseline is 3. The description adds meaning by explaining that a hostname is resolved progressively at each parent down to the registered domain, clarifying how the single 'domain' argument is interpreted beyond the schema text.

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 (Read) and resource (a domain's registration from its registry's RDAP server) and enumerates the returned content: statuses, registration/expiry/change dates, nameservers, DNSSEC delegation state. It explicitly distinguishes itself from the nearest sibling with 'Not for what DNS answers: check_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 an explicit when-not with a named alternative ('Not for what DNS answers: check_domain'), which is exactly the routing decision an agent needs. It also scopes the transport context (HTTPS via IANA RDAP bootstrap), reinforcing when this tool applies.

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

All isitdns toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources