eurodns-mcp

Update a mailbox password

eurodns_email_update_password

Idempotent

Set a new password for an email subscription's mailbox using its numeric id and matching password confirmation. The password is passed directly to the provider and not stored or logged.

Instructions

Sets a new password on the mailbox of the email subscription with that id, from body.password and body.passwordConfirmation, and returns the updated subscription. The value is written straight through to the provider and is neither stored nor logged here. Find the id with eurodns_subscription_get for product email; to change addresses rather than the password use eurodns_email_set_alias instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Numeric id of the email subscription, from eurodns_subscription_get with product email and no id.
`body`	Yes	password and passwordConfirmation, identical. The value is sent to the provider and never stored or logged here.

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.

Changed1 schema field changedv0.11.0Sep 8, 2026

changedInput schema / properties / id / description

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

Changed2 schema fields changedv0.10.0Sep 7, 2026

changedInput schema / properties / body / description

Previous value: -"Request body."New value: +"password and passwordConfirmation, identical. The value is sent to the provider and never stored or logged here."

addedInput schema / properties / id / description

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

First observedv0.9.1Sep 5, 2026

TDQS

A4.8/5.0

Behavior4/5

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

The description goes beyond the annotations by noting the value is written straight through to the provider and is never stored or logged. This adds meaningful context about data handling. The annotations already cover readOnly/destructive/idempotent hints, so the extra detail is a bonus.

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 compact and information-dense, consisting of two sentences that cover purpose, usage, and key caveats. No unnecessary words or redundant details are present.

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 moderate complexity, the description covers all necessary aspects: how to retrieve the identifier, what the body should contain, the behavior (write-through, no logging), and the result (returns updated subscription). The output schema is available, and the description mentions the returned object adequately.

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?

The schema fully describes both parameters, and the description enriches it by explaining that password and passwordConfirmation must be identical and that the value is sent to the provider without being stored or logged. This gives the agent more information than the raw schema alone.

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 sets a new password on the mailbox of the email subscription, using body.password and body.passwordConfirmation. It distinguishes itself from sibling tools like eurodns_email_set_alias and eurodns_email_set_catchall by focusing on password 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?

It explicitly explains when to use the tool (to change an email subscription password) and provides guidance on finding the id via eurodns_subscription_get. It also names the alternative for changing addresses (eurodns_email_set_alias), giving clear context for choosing among similar operations.

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

Deploy Server