Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update the validation approver of a certificate name

eurodns_ssl_update_validation_approver
Idempotent

Update SSL certificate validation method or approver for a specific SAN. Use when current approver cannot receive emails; only use approved addresses from get_validation.

Instructions

Changes the validation method or approver address for the name sanName of certificate certificateId, in SSL subscription subscriptionId, from body.verificationMethod and the approver it names, and returns the updated validation. Use it when the current approver cannot receive the email; only the addresses eurodns_ssl_get_validation lists are accepted, any other is refused. If the address is right and only the mail was lost, use eurodns_ssl_resend_approver_email instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesverificationMethod, and for email validation the approver address, chosen from the allowed approvers eurodns_ssl_get_validation lists.
sanNameYesSubject Alternative Name exactly as it appears on the certificate, e.g. www.example.com, from eurodns_ssl_get_certificate.
certificateIdYesNumeric id of the certificate inside the subscription, from the certificates eurodns_subscription_get returns for product ssl.
subscriptionIdYesNumeric id of the SSL subscription, from eurodns_subscription_get with product ssl and no id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResponse body as returned by the API.
statusYesUpstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.0
    • 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."
  2. Changed4 schema fields changedv0.10.0
    • changedInput schema / properties / body / description
      Previous value: -"Request body."New value: +"verificationMethod, and for email validation the approver address, chosen from the allowed approvers eurodns_ssl_get_validation lists."
    • 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."
  3. First observedv0.9.1

TDQS

A4.7/5.0
Behavior4/5

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

The description states that it changes the validation and returns the updated validation, matching the non-read-only annotation. It also mentions refusal of unapproved addresses, which adds useful behavioral context beyond the annotations, though it does not elaborate on all possible side effects.

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 fairly concise and front-loads the main action and object. The phrase 'from body.verificationMethod and the approver it names' is slightly awkward and could be clearer, but it does not add unnecessary length.

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?

The description, combined with the fully covered schema and sibling-tool references, gives enough context to call the tool correctly. It mentions return value, accepted input sources, and directs to related operations when alternative actions are appropriate.

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?

Every parameter is described with source and meaning: subscriptionId and certificateId explain where to obtain them, sanName gives an example, and the nested body explains verificationMethod and the approver constraint. The enum values for verificationMethod are also explained in the schema description.

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 verb 'Changes' and specifies the resource: validation method or approver address for a SAN of a certificate in an SSL subscription. It also distinguishes itself from the related resend operation, making the tool's purpose 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?

It explicitly says when to use the tool ('when the current approver cannot receive the email'), states the constraint that only addresses from eurodns_ssl_get_validation are accepted, and directs users to eurodns_ssl_resend_approver_email for the lost-mail case. This provides clear decision guidance.

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

Deploy Server

Other Tools