Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a domain, or search the account’s domains

eurodns_domain_get
Read-onlyIdempotent

Retrieve details for domains in your account using a specific domain name or search filters, including status, expiry, renewal, contacts, and nameservers. Returns 404 for unregistered names.

Instructions

Returns one domain already registered in this account — status, expiry, renewal method, contacts and nameservers — when domainName is given, or searches the account’s domains and returns one summary per match when it is omitted. It only knows domains held here: an unknown name answers 404 rather than an availability, so for a name you might register use eurodns_domain_check_availability instead. The search reads body for its filters and page and size for paging; a search without criteria lists the whole portfolio, which is the way to find a name you do not hold exactly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoSearch criteria, read only when domainName is omitted: a free-text term with its termMatchingMode and termMatchFields, plus boolean filters such as active, renewable, dnssecActivated or premiumDns. Omitted or empty, every domain is listed.
pageNo1-based page number. There is no page meaning everything: walk pages until a short one comes back.
sizeNoResults per page, 1 to 500. A wide page is truncated by the character limit, so prefer a filter to a large size.
sortFieldNoResult field to sort on, spelled as in the response items. Unsorted when omitted.
sortOrderNoASC or DESC; only read with sortField.
domainNameNoFully qualified name of a domain held in this account, e.g. example.com, to return in full. Omit it to search the account’s domains with body and the pagination arguments.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResponse body as returned by the API.
statusYesUpstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.11.0
    • addedInput schema / properties / body
      Added value: +{
+  "description": "Search criteria, read only when domainName is omitted: a free-text term with its termMatchingMode and termMatchFields, plus boolean filters such as active, renewable, dnssecActivated or premiumDns. Omitted or empty, every domain is listed.",
+  "properties": {
+    "active": {
+      "description": "If `true`, only non expired domains will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "contactValidated": {
+      "description": "If `true`, only domains where the owner contact has been validated will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "contactValidationExpiringSoon": {
+      "description": "Only domains with a contact validation close to expiring will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "contactValidationMethod": {
+      "enum": [
+        "EMAIL",
+        "NIS2"
+      ],
+      "type": "string"
+    },
+    "dnssecActivated": {
+      "description": "If `true`, only domains with an active DNSSEC protection will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "folderFullPath": {
+      "description": "Only domains with this exact folder path will be included",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pendingModification": {
+      "description": "If `true`, only domains with an ongoing operation will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "premium": {
+      "description": "If `true`, only premium domains will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "premiumDns": {
+      "description": "If `true`, only domains using our premium DNS solution will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "reactivable": {
+      "description": "If `true`, only reactivable domains will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "renewable": {
+      "description": "If `true`, only renewable domains will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "renewalMethod": {
+      "enum": [
+        "AUTORENEW",
+        "AUTOEXPIRE"
+      ],
+      "type": "string"
+    },
+    "term": {
+      "description": "The search term used to filter out results in combination with the `termMatchingMode` and `termMatchFields` parameters",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "termMatchFields": {
+      "items": {
+        "enum": [
+          "DOMAIN_NAME",
+          "FOLDER",
+          "CONTACTS",
+          "OWNER_CONTACT",
+          "ADMIN_CONTACT",
+          "TECHNICAL_CONTACT",
+          "BILLING_CONTACT",
+          "NAMESERVERS"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "termMatchingMode": {
+      "enum": [
+        "CONTAINS",
+        "STARTS_WITH",
+        "EXACTLY"
+      ],
+      "type": "string"
+    },
+    "tldName": {
+      "description": "The exact TLD name of a domain",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "useOurNameservers": {
+      "description": "If `true`, only domains using our nameserver configuration will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "whoisPrivacy": {
+      "description": "If `true`, only domains where domain privacy is activated will be included",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / properties / domainName / description
      Previous value: -"Fully qualified domain name, e.g. example.com, as listed by eurodns_domain_search."New value: +"Fully qualified name of a domain held in this account, e.g. example.com, to return in full. Omit it to search the account’s domains with body and the pagination arguments."
    • 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"
+}
    • removedInput schema / required
      Removed value: -[
-  "domainName"
-]
  2. Changed1 schema field changedv0.10.0
    • changedInput schema / properties / domainName / description
      Previous value: -"The exact domain name"New value: +"Fully qualified domain name, e.g. example.com, as listed by eurodns_domain_search."
  3. First observedv0.9.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this as read-only and idempotent, so the safety profile is covered. The description adds genuinely useful behavior beyond that: unknown names return 404 rather than availability, omitting domainName switches from exact get to search, and a search without filters returns the entire portfolio. There is no contradiction with the annotations.

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, front-loaded with the primary behavior, then the alternative tool, then search and paging behavior. Every sentence carries operational value with no filler or repetition of the schema.

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?

With an output schema and safety annotations already present, the description covers everything an agent needs: exact get mode, search mode, filter and paging references, no-criteria behavior, and the 404 case. It does not need to explain return values because the output schema supplies that.

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 detailed parameter descriptions already carry the main semantic load. The description does clarify that domainName selects exact-get mode while body, page, and size drive search mode, but that grouping is already stated in the schema, so it adds no substantial new parameter meaning.

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: it returns one registered account domain with status, expiry, renewal method, contacts, and nameservers when domainName is given, or searches the account's domains when it is omitted. It also explicitly distinguishes itself from eurodns_domain_check_availability, which prevents an agent from confusing lookup of held domains with availability checks.

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 an explicit when-to-use route: if a name might not be held yet, use eurodns_domain_check_availability instead, because this tool answers 404 for unknown names. It also explains that a search without criteria lists the whole portfolio, which is the intended way to find a name you do not know exactly.

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

Deploy Server

Other Tools