eurodns-mcp

Get a subscription, or search them across products

eurodns_subscription_get

Read-onlyIdempotent

Retrieve full subscription details by ID and product, list subscriptions for a product, or search all subscriptions with filters.

Instructions

Returns one subscription in full when product and id are given — an SSL subscription with its certificates, a mailbox with its aliases, a Premium DNS, Microsoft or HTTPS redirect term — lists one product’s subscriptions when only product is given, or searches every product when both are omitted. Start with the cross-product search for an expiry review, then narrow by product. It reads records only and manages nothing behind them; a filter marked for another product is ignored, and an id without product is refused before any call, since ids repeat across products. Its ids feed eurodns_ssl_get_certificate and eurodns_email_set_alias.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Numeric id of one subscription of the chosen product, from a previous search, to return in full. Omit it to list or search instead.
`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.
`product`	No	Which product to read: ssl, email, premium_dns, microsoft or https_redirect. Omit it to search every product at once with the common filters; required whenever id is given, because ids are only unique within a product.
`sanName`	No	ssl only: a Subject Alternative Name of a certificate in the subscription.
`userName`	No	email only: the mailbox user name, the part before the @.
`renewable`	No	ssl only: true keeps subscriptions that can still be renewed.
`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.
`commonName`	No	ssl only: the common name of a certificate in the subscription.
`domainName`	No	Keep only subscriptions attached to this domain, e.g. example.com. Read by the cross-product search and by the email and premium_dns listings; use microsoftDomain for Microsoft.
`accountLabel`	No	microsoft only: the account label the subscription was created under.
`microsoftDomain`	No	microsoft only: the Microsoft 365 domain of the subscription.
`autoRenewEnabled`	No	Cross-product search only: true keeps subscriptions that renew themselves, false only those that will lapse.
`subscriptionTypes`	No	Cross-product search only: keep these products, e.g. ["SSL", "EMAIL"]. Ignored when product is given, which already selects one.
`subscriptionStatus`	No	Keep only subscriptions in this lifecycle status, e.g. ACTIVE, TO_RENEW or PROVISIONING, for any product. Omit for every status.

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.

Addedv0.11.0Sep 8, 2026

TDQS

A5/5.0

Behavior5/5

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

The description states it reads records only and manages nothing behind them, aligning with readOnlyHint and destructiveHint false. It also discloses that an id without product is refused, filters marked for another product are ignored, and wide pages are truncated, giving clear expectations about side effects and boundaries.

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 dense but efficiently structured: it front-loads the core behavior, then gives a usage strategy, then covers constraints and edge cases. Every sentence contributes meaningful information without fluff or repetition.

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 rich input schema and annotations, the description covers all necessary operational details: pagination semantics, sorting, product-specific filters, cross-product filtering, id uniqueness, and the character-limit truncation caveat. There is no obvious gap that would prevent an agent from using the tool correctly.

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

Parameters5/5

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

While the schema descriptions are already detailed, the tool description adds crucial semantic context: ids are only unique within a product, certain filters are product-specific or ignored in other modes, and subscriptionTypes is ignored when a product is given. This goes well beyond the baseline and clarifies ambiguous parameters.

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 three modes of operation — fetch one subscription with product and id, list one product's subscriptions with product alone, or search across every product when both are omitted — and gives concrete examples of what each subscription type contains. It fully distinguishes this read operation from the many sibling tools.

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 explicitly recommends starting with the cross-product search for an expiry review and then narrowing by product, which is actionable guidance. It also notes which filters apply to which product searches and warns about pagination and character-limit truncation, so an agent knows how to use the tool correctly.

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

Deploy Server