eurodns-mcp

Get a TLD, or list them

eurodns_tld_get

Read-onlyIdempotent

Check TLD registration terms and registry requirements by ID, or list orderable TLDs filtered by name.

Instructions

Returns one TLD by id — registration terms, minimum and maximum durations, registry-specific requirements — or lists the TLDs this account can order when id is omitted, filtered by tldName and paged. Read it before ordering an unfamiliar extension to learn what the registry demands. The full list runs to hundreds of entries, so filter with tldName or page with size rather than asking for everything; it says nothing about whether a name is free, which is eurodns_domain_check_availability.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Numeric id of the TLD to return. Omit it to list the TLDs this account can order, optionally filtered by tldName.
`page`	No	1-based page number. There is no page meaning everything: walk pages until a short one comes back.
`size`	No	Results per page, 1 to 500. A wide page is truncated by the character limit, so prefer a filter to a large size.
`tldName`	No	Filter on the TLD name, e.g. "com" or "lu". Omit to page through every TLD.
`sortField`	No	Result field to sort on, spelled as in the response items. Unsorted when omitted.
`sortOrder`	No	ASC or DESC; only read with sortField.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Response body as returned by the API.
`status`	Yes	Upstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.10.0Sep 7, 2026

changedInput schema / properties / id / description

Previous value: -"id of TLD to return"New value: +"Numeric id of the TLD to return. Omit it to list the TLDs this account can order, optionally filtered by tldName."

addedInput schema / properties / page

Added value: +{
+  "description": "1-based page number. There is no page meaning everything: walk pages until a short one comes back.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / size

Added value: +{
+  "description": "Results per page, 1 to 500. A wide page is truncated by the character limit, so prefer a filter to a large size.",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / sortField

Added value: +{
+  "description": "Result field to sort on, spelled as in the response items. Unsorted when omitted.",
+  "type": "string"
+}

addedInput schema / properties / sortOrder

Added value: +{
+  "description": "ASC or DESC; only read with sortField.",
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}

addedInput schema / properties / tldName

Added value: +{
+  "description": "Filter on the TLD name, e.g. \"com\" or \"lu\". Omit to page through every TLD.",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "id"
-]
```

First observedv0.9.1Sep 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: the list can be very large, results are pageable, omitting id switches to list mode, and the tool says nothing about domain availability.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences with no filler, front-loads the core behavior, and each sentence earns its place: what it returns, when to use it, and what it explicitly does not do. The sibling reference is tightly interwoven rather than bolted on.

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?

For a read-only, idempotent list/get tool with a rich input schema and an output schema, the description covers the essential decision points: how to get one vs. many, how to avoid overwhelming responses, and what it cannot tell you. No critical contextual gap remains.

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?

Input schema description coverage is 100%, so the schema already explains all six parameters clearly. The description does add strategic emphasis around id omission, tldName filtering, and paging, but it does not add significant semantic detail that the schema lacks, so the baseline of 3 is appropriate.

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 (Returns/lists), a clear resource (TLDs), and the conditional behavior based on whether id is provided. It also explicitly names the sibling tool it is not, eurodns_domain_check_availability, so an agent can immediately distinguish the two without inspecting schemas.

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?

The description gives explicit usage context: read this before ordering an unfamiliar extension to learn registry requirements. It also warns against asking for the entire list and recommends filtering by tldName or paging with size, and explicitly routes availability questions to eurodns_domain_check_availability.

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

Deploy Server