addy-mcp

create_alias

Create a new email alias for a selected domain, with optional custom local part, format, labels, and forwarding recipients. Use it to generate addresses for signups or privacy.

Instructions

Create a new alias. Use get_domain_options to see which domains are available.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "create_alias"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	Domain for the alias, e.g. 'anonaddy.me' or a custom domain/username domain
`format`	No	Alias format. 'custom' requires local_part and a custom domain or username domain.
`label_ids`	No	Labels to attach
`local_part`	No	The part before the @ (only with format='custom')
`description`	No	What the alias is for, e.g. 'Amazon'
`recipient_ids`	No	Recipients to forward to (default recipient if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Nov 12, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write-safe profile is covered. The description adds only the domain lookup pointer and says nothing about whether the alias is immediately active, what happens if the domain or local part is invalid, or whether creation fails on duplicates.

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?

Two short sentences, front-loaded with the action and followed by the prerequisite. Nothing is wasted, though the brevity leaves the definition thin rather than optimally sized for a six-parameter creation tool.

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

Completeness3/5

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

With full schema coverage and annotations, the description covers enough to invoke the tool. It is incomplete for a creation tool in that it never says what is produced (the generated alias address) or how defaults such as the default recipient are applied.

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 description coverage is 100%, so every parameter including format, local_part, recipient_ids and label_ids is already documented in the schema. The description adds no meaning beyond it, which is the baseline 3 for fully documented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description leads with a specific verb and resource ('Create a new alias'), which is clearly distinct from siblings like update_alias, delete_alias or bulk_alias_action. It does not, however, explicitly contrast itself with those siblings, so it stops short of a 5.

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

Usage Guidelines3/5

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

It gives one concrete usage precondition: call get_domain_options first to learn which domains are valid. It offers no when-not guidance, no note about format='custom' prerequisites, and no mention of alternatives for creating aliases in bulk.

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

Deploy Server