eurodns-mcp

Get a nameserver profile, or list them

eurodns_nameserver_get_profile

Read-onlyIdempotent

Retrieve a nameserver profile by ID or list all profiles with optional filters for default, deletable, pagination, sorting, and inclusion of nameservers. Helps identify the right profile for domain configuration.

Instructions

Returns one reusable nameserver set by id, or lists the account’s nameserver profiles when id is omitted, with the default one and the deletable ones marked and, with includeNameservers, each profile’s servers. Use it to find the profile a domain should point at, or the id eurodns_nameserver_save_profile takes; it does not say which profile a given domain uses, which eurodns_domain_get returns. Filter with default or deletable rather than paging the whole list.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Numeric id of the nameserver profile to return. Omit it to list the account’s profiles with the filters below.
`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.
`default`	No	true keeps only the default profile, false keeps every other one. Omit for both.
`deletable`	No	true keeps only profiles no domain uses, which are the ones that can be deleted.
`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.
`includeNameservers`	No	Include each profile's nameserver list in the response, not just its name and id.

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.

Changed9 schema fields changedv0.10.0Sep 7, 2026

addedInput schema / properties / default

Added value: +{
+  "description": "true keeps only the default profile, false keeps every other one. Omit for both.",
+  "type": "boolean"
+}

addedInput schema / properties / deletable

Added value: +{
+  "description": "true keeps only profiles no domain uses, which are the ones that can be deleted.",
+  "type": "boolean"
+}

addedInput schema / properties / id / description

Added value: +"Numeric id of the nameserver profile to return. Omit it to list the account’s profiles with the filters below."

addedInput schema / properties / includeNameservers

Added value: +{
+  "description": "Include each profile's nameserver list in the response, not just its name and id.",
+  "type": "boolean"
+}

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: -[
-  "id"
-]
```

First observedv0.9.1Sep 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description supplements the readOnlyHint annotation by explaining pagination behavior ('walk pages until a short one comes back') and the truncation effect of wide pages. It does not contradict the annotations, which already cover read-only and idempotent semantics. It adds useful detail about response shape without repeating the annotation flags.

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?

The description is two sentences and front-loads the core purpose before adding usage and filtering guidance. It is somewhat talkative with commas and parentheticals but remains scannable and every clause carries meaning. It earns a high score for being compact while dense with decision-relevant 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 8 optional parameters and no required ones, the description covers the core decision points: when to use this versus the save counterpart, how to filter, and how pagination behaves. There is an output schema, so return value details do not need to be in the description. The description adequately guides an agent through the main usage scenarios without needing to enumerate every parameter.

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 baseline is 3. The description adds only marginal value beyond the schema: it explains the task-level intent (find the profile a domain points at) but does not clarify parameter interactions beyond what the schema already states. The parameter descriptions themselves are already thorough, so the description does not need to add much.

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 clearly states the resource: reusable nameserver sets/profiles. It distinguishes the singular (get by id) from the plural (list all) behavior, and explicitly names the sibling tool eurodns_nameserver_save_profile as the counterpart. The verb 'Returns' and the resource 'nameserver profiles' are both precise and specific.

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 direct usage guidance: use it to find the profile a domain should point at, or the id that save_profile takes. It also explicitly notes what this tool does NOT tell you (which profile a domain uses, directing to eurodns_domain_get), which is especially valuable for disambiguation. It additionally recommends filters over paging.

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

Deploy Server