domain-suite-mcp

Overview Schema Source Related Servers Discussions Admin

setup_mx

Configure MX records for your domain by selecting a mail provider template. Supports Google, Resend, SendGrid, Mailgun, SES, ProtonMail, and custom entries.

Instructions

Configure MX records with mail provider template

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>",
      "mailProvider": "<mailProvider>"
    },
    "name": "setup_mx"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes
`provider`	No	DNS provider (auto-detected if omitted)
`mailProvider`	Yes
`customRecords`	No	Required when mailProvider is 'custom'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 12, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Without annotations, the description should disclose side effects like record replacement or permissions, but it only says 'configure', leaving behavior unclear.

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?

Single sentence with no extraneous words; efficient and to the point.

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 4 parameters, one conditional, and no output schema, the description lacks details on success, failure, idempotency, or return values, making it incomplete for an agent.

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?

Schema coverage is 50%, but the description adds no insight beyond parameter names, failing to clarify the role of 'provider' or the 'customRecords' conditional requirement.

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 configures MX records using a mail provider template, which is specific and distinguishes it from sibling DNS setup tools like setup_dkim.

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 on when to use this tool versus alternatives like setup_dkim or setup_spf, nor any exclusion criteria or prerequisites.

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