Skip to main content
Glama
Sign In
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Register Email Sending Domain

create-email-domain

Register a sending domain and get the DNS records to publish at your DNS provider. It stays pending until verified, so publish each returned record, then verify.

Instructions

Register a domain to send email from and get the DNS records to publish at its DNS provider. The domain starts pending and cannot send until it is verified. This server cannot change DNS: give the user every record exactly as returned (type, name and value), saying which are required, then call verify-email-domain once they have published them. Registering a domain the organization already has returns its current state, and only one domain can be registered at a time.

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": {
      "name": "<name>"
    },
    "name": "create-email-domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe domain to send from, e.g. mail.acme.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the generic non-read-only, non-destructive, non-idempotent profile; the description adds the real behavioral facts: a pending→verified state machine, that sending is blocked until verified, that the caller must relay every record verbatim with required flags, and that the server performs no DNS mutation. The re-registration behavior (returns current state) is also disclosed, which is exactly the kind of context annotations cannot carry.

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?

Four tight sentences, front-loaded with the action and its output, followed by the constraint and the edge case. Every sentence carries operational information; nothing is restated from the schema or title.

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?

With no output schema, the description takes on the burden of describing the return value and does so (records with type, name, value and required flags). It also covers the lifecycle, the blocking condition, the hand-off protocol, and the duplicate-registration case, leaving nothing an agent needs before calling.

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 coverage is 100% and the single `name` parameter already carries a format example (mail.acme.com). The description confirms the domain is the sending origin but adds no format or validation detail beyond the schema, so the baseline 3 is appropriate.

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?

States a specific verb+resource ("Register a domain to send email from") and immediately names the secondary output (DNS records). It distinguishes itself from siblings by naming verify-email-domain as the follow-up step, so an agent can tell registration apart from verification without opening either schema.

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?

Gives explicit when-to-use sequencing: register, hand the records to the user, then call verify-email-domain once published. It also states exclusions and edge cases — the server cannot change DNS, and only one domain can be registered at a time — which prevents misuse rather than leaving it to inference.

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