Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get an email subscription, or search them

eurodns_email_get_subscription
Read-onlyIdempotent

Fetch a single email subscription's mailbox, aliases, and catch-all state by ID, or search subscriptions by status, domain, or username. Use the returned ID for alias, catch-all, or password updates.

Instructions

Returns one email subscription — the mailbox, its aliases and catch-all state — by id, or searches the account’s email subscriptions by status, domain and user name when id is omitted. Its id is what eurodns_email_set_alias, eurodns_email_set_catchall and eurodns_email_update_password take; every product at once is eurodns_subscription_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric id of the email subscription to return. Omit it to search the account’s email subscriptions 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.
userNameNoFilter on the mailbox user name, the part before the @.
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 email 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 email subscription(s) you search for are related to",
+  "type": "string"
+}
    • addedInput schema / properties / id / description
      Added value: +"Numeric id of the email subscription to return. Omit it to search the account’s email subscriptions with the filters below."
    • 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 / 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"
+}
    • addedInput schema / properties / userName
      Added value: +{
+  "description": "Filter on the mailbox user name, the part before the @.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "id"
-]
  2. First observedv0.9.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the bar for additional disclosure is lower. The description still adds value by revealing the dual get/search behavior, the specific data returned (mailbox, aliases, catch-all state), and the id's role across sibling tools, all beyond what the annotations state.

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 dense sentences carry all essential information without redundancy. The primary behavior is front-loaded, and the sibling differentiation and cross-tool id mapping are packed tightly but efficiently, with no filler.

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?

Given the tool's dual mode, eight parameters, and existing output schema, the description covers the essential context: what is returned, when each mode applies, what filters are relevant, and how this tool relates to the mutation siblings. Nothing critical is missing for an agent to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents every parameter individually. The description adds meaningful cross-tool semantics by stating that the id returned here is exactly what eurodns_email_set_alias, eurodns_email_set_catchall, and eurodns_email_update_password expect, and that omitting id switches to search mode with filters.

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 precise verb ('Returns one email subscription ... or searches') with an explicit resource and result content: the mailbox, aliases, and catch-all state. It also distinguishes itself from siblings by naming eurodns_subscription_search as the alternative for every product at once.

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?

It clearly explains when to use the get mode versus the search mode: provide id for a single subscription, omit id to search by status, domain, and user name. It also tells the agent that the id is the same one consumed by the alias, catch-all, and password mutation tools, and directs broader queries to eurodns_subscription_search.

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