Skip to main content
Glama
Michaelzag

Migadu MCP Server

by Michaelzag

reset_mailbox_password

Idempotent

Reset password for one or more mailboxes by providing the target identifier and new password.

Instructions

Reset mailbox password(s). List of dicts with: target, new_password.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes

Implementation Reference

  • The actual implementation of reset_mailbox_password in the service layer. It calls the Migadu API PUT endpoint for the mailbox with the new password in the JSON body.
    async def reset_mailbox_password(
        self, domain: str, local_part: str, new_password: str
    ) -> dict[str, Any]:
        return await self.client.put(
            f"/domains/{domain}/mailboxes/{local_part}",
            json={"password": new_password},
        )
  • The MCP tool handler for reset_mailbox_password. It parses the target email, delegates to the mailbox service, and returns a success response.
    @migadu_bulk_tool(mcp, MailboxPasswordResetRequest, entity="password reset")
    async def reset_mailbox_password(
        item: MailboxPasswordResetRequest, ctx: Context
    ) -> dict[str, Any]:
        """Reset mailbox password(s). List of dicts with: target, new_password."""
        domain, local_part = parse_email_target(item.target)[0]
        email = format_email_address(domain, local_part)
        await ctx.info(f"📋 Resetting password for {email}")
        await (
            get_service_factory()
            .mailbox_service()
            .reset_mailbox_password(domain, local_part, item.new_password)
        )
        return {"reset": email, "success": True}
  • Pydantic schema for MailboxPasswordResetRequest defining the target email and new_password fields.
    class MailboxPasswordResetRequest(BaseModel):
        target: str = Field(..., description="Email address or local part")
        new_password: str = Field(..., description="New password for authentication")
  • The function reference used to keep the tool registered in the FastMCP instance (within the register_mailbox_tools function).
        reset_mailbox_password,
        set_autoresponder,
    )
Behavior2/5

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

The description does not disclose behavioral traits beyond the basic action. Key side effects (e.g., invalidating existing sessions, needing new login) are not mentioned. The annotations provide some hints (idempotentHint true, openWorldHint true), but the description itself adds no behavioral context.

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 very short (one sentence), which is efficient but omits essential details about the parameter structure. It could be slightly longer to improve clarity without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema), the description should be sufficient, but it fails to explain the inner structure of the array items or any behavioral effects. Annotations cover some gaps but not all.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has a single array parameter with no inner structure defined. The description mentions the dictionary fields 'target' and 'new_password' but does not specify types, formats, or constraints. With 0% schema coverage, the description should provide more detail; it does so minimally.

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 explicitly states the action ('Reset mailbox password') and indicates it can handle multiple passwords via plural '(s)'. This clearly distinguishes it from sibling tools like update_mailbox, which might update other settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like update_mailbox, nor any prerequisites or conditions (e.g., user must have admin rights). The description lacks context for appropriate invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Michaelzag/migadu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server