eurodns-mcp

Get the validation of a certificate name

eurodns_ssl_get_validation

Read-onlyIdempotent

Check the validation status for a SAN in an SSL certificate. See the method, approver address, and required token or record to complete issuance.

Instructions

Returns how the name sanName of certificate certificateId, in SSL subscription subscriptionId, is being validated — method, approver address, token or record to publish — and where it stands. Read it when an ordered certificate has not been issued; it also lists the approver addresses the authority accepts. To change the method or approver use eurodns_ssl_update_validation_approver, and to send the email again use eurodns_ssl_resend_approver_email rather than this call, which sends nothing.

Input Schema

TableJSON Schema

Name	Required	Description
`sanName`	Yes	Subject Alternative Name exactly as it appears on the certificate, e.g. www.example.com, from eurodns_ssl_get_certificate.
`certificateId`	Yes	Numeric id of the certificate inside the subscription, from the certificates eurodns_subscription_get returns for product ssl.
`subscriptionId`	Yes	Numeric id of the SSL subscription, from eurodns_subscription_get with product ssl and no 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.

Changed2 schema fields changedv0.11.0Sep 8, 2026

changedInput schema / properties / certificateId / description

Previous value: -"Numeric id of the certificate inside the subscription, from the certificates eurodns_ssl_get_subscription returns."New value: +"Numeric id of the certificate inside the subscription, from the certificates eurodns_subscription_get returns for product ssl."

changedInput schema / properties / subscriptionId / description

Previous value: -"Numeric id of the SSL subscription, from the list eurodns_ssl_get_subscription returns when called without an id."New value: +"Numeric id of the SSL subscription, from eurodns_subscription_get with product ssl and no id."

Changed3 schema fields changedv0.10.0Sep 7, 2026

addedInput schema / properties / certificateId / description

Added value: +"Numeric id of the certificate inside the subscription, from the certificates eurodns_ssl_get_subscription returns."

addedInput schema / properties / sanName / description

Added value: +"Subject Alternative Name exactly as it appears on the certificate, e.g. www.example.com, from eurodns_ssl_get_certificate."

addedInput schema / properties / subscriptionId / description

Added value: +"Numeric id of the SSL subscription, from the list eurodns_ssl_get_subscription returns when called without an id."

First observedv0.9.1Sep 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already indicate read-only, open-world, idempotent, and non-destructive behavior. The description reinforces that this call 'sends nothing' and only returns validation state, aligning with annotations without contradiction.

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 concise and well-structured, with the primary purpose stated first and supplementary guidance included naturally. Every sentence adds useful context without redundancy.

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 sufficiently explains when to use the tool and what it returns, and the output schema exists to describe the result structure. It does not detail all possible validation states, but this is not critical given the output schema and read-only nature.

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?

All three parameters have descriptions providing source context (from subscription_get or certificate list) and type details. The schema coverage is 100%, and the descriptions clarify how to obtain the IDs, though they rely on referencing other tool outputs.

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 tool returns validation details for a specific certificate name, including method, approver address, and token/record to publish. It also distinguishes this read operation from update and resend actions.

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?

The description explicitly advises using this tool when an ordered certificate has not been issued, and mentions alternatives for changing the approver or resending email. It does not exhaustively list all alternate tools, but provides clear context for the primary use case.

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

Deploy Server