eurodns-mcp

Get an SSL certificate

eurodns_ssl_get_certificate

Read-onlyIdempotent

Retrieve detailed information about a specific SSL certificate using its subscription and certificate IDs, including common name, SANs, validity, and issuance status.

Instructions

Returns one certificate of the SSL subscription subscriptionId by certificateId: common name, SANs, validity dates, issuance status and the certificate itself once issued. Both ids come from eurodns_subscription_get for product ssl, which lists the certificates of a subscription. It does not say how a pending name is being validated: for that use eurodns_ssl_get_validation instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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."

Changed2 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 / 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.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds context about the returned certificate contents without contradicting the annotations, but does not elaborate on other behaviors like error cases or side effects beyond what is implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose and repetitive, particularly the second sentence which reiterates the source of the IDs. It conveys necessary information but could be more concise without losing clarity.

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?

Given that an output schema exists, the description appropriately focuses on input sourcing and differentiation. It covers the essential context for using the tool correctly, including where to obtain IDs and what it does not handle (validation). The only minor gap is not explicitly stating that the output schema describes the return format, but that is implied by the existence of the output 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 covers 100% of parameters with descriptive text about their source and meaning. The description repeats the schema information without adding new semantic details, so it stays at the baseline score for full schema coverage.

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?

Clearly states the tool returns a single certificate with specific fields (common name, SANs, validity, status, certificate), and distinguishes it from sibling tools like validation retrieval. The verb 'Returns' is specific and the resource 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 Guidelines5/5

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

Explicitly instructs that both IDs come from eurodns_subscription_get for SSL products, and clarifies that validation status is handled by eurodns_ssl_get_validation, providing clear when-to-use guidance and differentiation from related tools.

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

Deploy Server