Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get a Premium DNS subscription, or search them

eurodns_premium_dns_get_subscription
Read-onlyIdempotent

Retrieve a Premium DNS subscription by ID to check its status, term, and domain, or search subscriptions by status and domain when no ID is provided.

Instructions

Returns one Premium DNS subscription with its status, term and domain by id, or searches the account’s Premium DNS subscriptions by status and domain when id is omitted. Use it to check a renewal date or before changing a plan; eurodns_subscription_search covers every product at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric id of the Premium DNS subscription to return. Omit it to search them by status and domain.
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.
domainNameNoThe domain name the Premium DNS subscription(s) you search for are related to
subscriptionStatusNoKeep only subscriptions in this lifecycle status, e.g. ACTIVE, TO_RENEW or PROVISIONING. Omit for every status.

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 / domainName
      Added value: +{
+  "description": "The domain name the Premium DNS subscription(s) you search for are related to",
+  "type": "string"
+}
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Numeric id of the Premium DNS subscription to return. Omit it to search them by status and domain.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • 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 / properties / subscriptionId
      Removed value: -{
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • addedInput schema / properties / subscriptionStatus
      Added value: +{
+  "description": "Keep only subscriptions in this lifecycle status, e.g. ACTIVE, TO_RENEW or PROVISIONING. Omit for every status.",
+  "enum": [
+    "ACTIVE",
+    "TO_RESTORE",
+    "TO_RENEW",
+    "TO_DELETE",
+    "PENDING_RENEW",
+    "PENDING_RENEW_DOWNGRABLE",
+    "UPGRADE_QUANTITY",
+    "PENDING_UPGRADE_PRODUCT",
+    "HOLD",
+    "PENDING_DOWNGRADE_PRODUCT",
+    "MIGRATED",
+    "PENDING_REACTIVATE",
+    "PROVISIONING"
+  ],
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "subscriptionId"
-]
  2. First observedv0.9.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), lowering the bar. The description adds meaningful behavioral context beyond annotations: the id-omitted search mode switch, the returned fields (status, term, domain), and the account-scoped search. No contradiction with 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 with zero waste. The primary fetch-by-id behavior is front-loaded, the search mode follows naturally, and the usage guidance and sibling distinction wrap up in the second sentence.

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?

Complete for a read-only list/fetch tool: 0 required params, full schema coverage, output schema present, rich annotations, and a description that covers purpose, both operation modes, use cases, and the sibling alternative. Nothing an agent needs to invoke it correctly 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% — all 7 parameters carry their own descriptions, so the schema does the heavy lifting. The description alludes to status/domain filtering and id omission, but adds little param-specific meaning beyond what the schema already states. Baseline 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+resource ('Returns one Premium DNS subscription... by id, or searches...'), states the dual-mode behavior clearly, and names the alternative (eurodns_subscription_search) that covers every product. An agent can tell what this tool does and how it differs from related subscription tools without opening the schema.

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?

Gives explicit use cases ('check a renewal date or before changing a plan') and an explicit routing rule with a selection condition: eurodns_subscription_search when every product needs to be covered at once. This is exactly the kind of when-to-use vs alternative guidance agents need.

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