eurodns-mcp

Reissue an SSL certificate

eurodns_ssl_reissue_certificate

Reissue an SSL certificate using a new CSR after key rotation, without extra charge or changing the expiry date. Provide subscription ID, certificate ID, and the encoded CSR to receive a new certificate.

Instructions

Reissues certificate certificateId of the SSL subscription subscriptionId against the new body.encodedCsr, for example after a key rotation, and returns the new certificate. No charge is made and the term does not move: extending it is a separate, paid renewal rather than a reissue. Names added in body.sanEntries go through validation again, which eurodns_ssl_get_validation follows; both ids come from eurodns_subscription_get for product ssl.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	Yes	encodedCsr: the new PEM certificate request the certificate is reissued against, plus sanEntries for a multi-domain 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

changedInput schema / properties / body / description

Previous value: -"Request body."New value: +"encodedCsr: the new PEM certificate request the certificate is reissued against, plus sanEntries for a multi-domain certificate."

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.4/5.0

Behavior4/5

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

Annotations already mark this as a mutating, non-destructive operation. The description adds material behavior beyond that: no charge is made, the subscription term does not move, SAN entries are re-validated, and the tool returns the new certificate. These are important operational facts not visible in the annotations.

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

Conciseness4/5

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

The description is four sentences, front-loaded with the core action and key parameters, then adds behavioral caveats about charge, term, and validation. It is information-dense but each sentence earns its place; slightly dense phrasing keeps it from a 5.

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?

For a three-parameter mutation with a nested body and an output schema, the description covers the trigger scenario, id provenance, validation follow-up, commercial impact, and return value. Nothing an agent needs to decide whether to invoke it or how 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 coverage is 100%, and the schema already documents all three parameters in detail, including the nested body fields and the origin of both ids. The description reinforces this with usage context but adds little semantic meaning beyond what the schema already provides, so the baseline of 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?

States a specific action verb ('Reissues') with the exact resource (certificateId of SSL subscription) and input (body.encodedCsr). It explicitly contrasts reissue with a paid renewal, which distinguishes it from related SSL lifecycle operations like renewal or validation updates.

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 a concrete use case ('after a key rotation'), explicitly says extending the term is a separate paid renewal rather than a reissue, and directs the agent to eurodns_subscription_get for ids and eurodns_ssl_get_validation for the validation flow. This is strong when-vs-when-not guidance.

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

Deploy Server