Unique Domains

Every root TLD with its registry facts and launch phases

ud_list_tlds

Read-onlyIdempotent

Every root TLD with its registry facts and launch phases, alphabetical. Every input is optional; limit sets the page size.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ud_list_tlds"
  }
}

Input Schema

Name	Required	Description
`isIdn`	No	Internationalised endings only (`true`) or none (`false`).
`limit`	No	Page size, 20 at most.
`cursor`	No	The `meta.cursor` of the previous page.
`fields`	No	Comma-separated top-level keys to keep: tld, slug, ianaStatus, kind, ianaType, registryOperator, registryCountryCode, isBrand, isIdn, delegatedOn, removedOn, contractTerminated, rdapServer, category, phases, insights.
`country`	No	The registry operator's country, ISO 3166-1 alpha-2.
`isBrand`	No	Brand TLDs only (`true`) or none (`false`).
`ianaType`	No	IANA's own type word (`generic`, `country-code`, `sponsored`, `infrastructure`).
`publicSet`	No	`true`: the public set only (v1's `listing=public`).
`ianaStatus`	No	IANA root zone status.

Output Schema

Name	Required	Description
`data`	No
`meta`	No	The day of the answer, and the page cursor of a list.
`links`	No	Links of the answer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedOutput schema / properties / data / items / properties / insights / anyOf

Previous value: -[
-  {
-    "properties": {
-      "insightUrl": {
-        "type": "string"
-      },
-      "market": {
-        "anyOf": [
-          {
-            "properties": {
-              "availableOneWord": {
-                "description": "One-word names available on the ending.",
-                "type": "integer"
-              },
-              "cheapestRegistrar": {
-                "anyOf": [
-                  {
-                    "description": "Registrar catalog slug of the cheapest first year.",
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "computedAt": {
-                "description": "Timestamp of the rollup.",
-                "type": "string"
-              },
-              "medianBuy": {
-                "anyOf": [
-                  {
-                    "description": "Median first-year price.",
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "medianRenew": {
-                "anyOf": [
-                  {
-                    "description": "Median renewal price.",
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "registrations90d": {
-                "description": "Names registered in 90 days among those tracked.",
-                "type": "integer"
-              },
-              "sales12m": {
-                "description": "Usable sales, rolling 365 days.",
-                "type": "integer"
-              },
-              "salesMedian12mUsd": {
-                "anyOf": [
-                  {
-                    "description": "Median sale over 12 months, from three sales.",
-                    "type": "integer"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "salesTrend": {
-                "anyOf": [
-                  {
-                    "description": "12-month count against the previous 12 months, ±10 % threshold."
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "insightUrl": {
+        "type": "string"
+      },
+      "market": {
+        "anyOf": [
+          {
+            "properties": {
+              "availableOneWord": {
+                "description": "One-word names available on the ending.",
+                "type": "integer"
+              },
+              "cheapestRegistrar": {
+                "anyOf": [
+                  {
+                    "description": "Registrar catalog slug of the cheapest first year.",
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "computedAt": {
+                "description": "When these figures were computed.",
+                "type": "string"
+              },
+              "medianBuy": {
+                "anyOf": [
+                  {
+                    "description": "Median first-year price.",
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "medianRenew": {
+                "anyOf": [
+                  {
+                    "description": "Median renewal price.",
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "registrations90d": {
+                "description": "Names registered in 90 days among those tracked.",
+                "type": "integer"
+              },
+              "sales12m": {
+                "description": "Usable sales, rolling 365 days.",
+                "type": "integer"
+              },
+              "salesMedian12mUsd": {
+                "anyOf": [
+                  {
+                    "description": "Median sale over 12 months, from three sales.",
+                    "type": "integer"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "salesTrend": {
+                "anyOf": [
+                  {
+                    "description": "12-month count against the previous 12 months, ±10 % threshold."
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedNov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side effects are covered. The description adds ordering (alphabetical) and the optionality of all filters, but says nothing about default page size, cursor paging flow, or how filters combine, which is the extra context a list tool benefits from.

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 short sentences, front-loaded with the resource and scope. The second sentence about optional inputs is slightly redundant with the zero-required-params schema but still helps an agent quickly confirm no filters are mandatory.

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 an output schema present and full schema description coverage, the description need only frame the resource and filtering model, which it does. Minor gaps remain around ordering ties, paging default of 20, and what 'launch phases' contains, but nothing required for a correct call is missing.

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 all nine parameters, including the ianaStatus enum and the fields projection, are already documented. The description only restates that limit sets the page size, adding no meaning beyond the schema. 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?

States a specific resource and scope: 'Every root TLD with its registry facts and launch phases, alphabetical.' An agent knows exactly what the tool returns, but nothing distinguishes it from nearby siblings such as ud_list_tld_phases or ud_get_tld.

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?

'Every input is optional' implies the tool lists the full catalog by default and filters on request, which is useful implied usage. There is no explicit when-to-use versus siblings like ud_get_tld (single TLD) or ud_list_tld_phases (phases only), 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 Unique Domains 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.