Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get a nameserver profile, or list them

eurodns_nameserver_get_profile
Read-onlyIdempotent

Retrieves a reusable nameserver set by its ID, or lists account nameserver profiles when no ID is given. Use it to identify which profile to assign to a domain.

Instructions

Returns one reusable nameserver set by id, or lists the account’s nameserver profiles when id is omitted, with the default and deletable ones marked. Use it to find the profile a domain should point at; eurodns_nameserver_save_profile creates or rewrites one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric id of the nameserver profile to return. Omit it to list the account’s profiles with the filters below.
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.
defaultNotrue keeps only the default profile, false keeps every other one. Omit for both.
deletableNotrue keeps only profiles no domain uses, which are the ones that can be deleted.
sortFieldNoResult field to sort on, spelled as in the response items. Unsorted when omitted.
sortOrderNoASC or DESC; only read with sortField.
includeNameserversNoInclude each profile's nameserver list in the response, not just its name and id.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv0.10.0
    • 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"
-]
  2. First observedv0.9.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover read-only, idempotent, non-destructive behavior, so the description only needs to add non-safety behavior. It adds the dual id-or-list behavior, the default/deletable marking, and the relationship to save_profile. This is useful context beyond 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?

Two sentences, front-loaded with the core behavior, then a practical use case and sibling differentiation. Every clause earns its place and there is no filler or repetition of schema content.

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?

The description is complete for an agent to select and call the tool: it explains dual-mode behavior, the list markers, and the save alternative. The output schema exists, so return values need not be described, and all parameter semantics live in the input schema. Minor gaps like pagination nuance are already present in the schema.

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 the high-level meaning of omitting id ('lists the account's nameserver profiles'), while detailed parameter semantics like page size and filtering are already fully documented in the schema. This is adequate but not compensatory beyond schema.

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 states a clear dual behavior: returns one nameserver set by id, or lists all profiles when id is omitted, and notes the default/deletable markers. It distinguishes itself from eurodns_nameserver_save_profile, which is the obvious sibling, and the resource (nameserver profiles) is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete use case: 'Use it to find the profile a domain should point at' and names the alternative save_profile for creating/rewriting. It does not spell out explicit when-not conditions, but the contrast with the save sibling gives an agent enough routing guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JigSawFr/eurodns-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server