Ballast - Cold Email

Official

Overview Schema Source Related Servers Discussions Admin

add_domain

Connect a new sending domain to your Ballast workspace and verify DNS and deliverability records (MX, SPF, DKIM, DMARC, blacklists). Use when setting up a custom cold-email domain.

Instructions

Connect a new sending domain to the workspace and verify DNS. Registers a new sending domain under the workspace, saves it, and immediately initiates DNS and deliverability verification (MX, SPF, DKIM, DMARC, blacklists). USE THIS when setting up a new custom domain to send cold emails from Ballast. DO NOT use to test an external or unverified domain without adding it to the workspace (use check_domain instead) or to list existing domains (use list_domains instead).

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": "add_domain"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does well: it discloses that the call mutates state (registers and saves the domain) and that verification is initiated immediately with a named checklist (MX, SPF, DKIM, DMARC, blacklists). It does not say whether verification is synchronous or async, what happens on duplicate domains, or whether the operation is reversible/removable, which keeps it short of a 5 for an unannotated mutation tool.

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?

Front-loaded with the action, then the mechanics, then routing guidance — a logical order with no filler. The 'DO NOT' sentence is somewhat long, but each clause carries distinct routing information that an agent needs.

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

Completeness4/5

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

For a one-parameter mutation tool with no annotations and no output schema, the description covers the action, side effects, verification scope, and sibling routing well. The remaining gap is post-call behavior: nothing about duplicate-domain errors, verification latency, or what the caller gets back.

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 0%, so the description must compensate for the single 'domain' parameter, and it only partially does: it implies the value must be a domain the user owns and that gets added to the workspace, but gives no format guidance (bare apex domain vs. subdomain vs. URL, no protocol). The schema contributes only a maxLength constraint.

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 ('Connect a new sending domain to the workspace') and immediately elaborates the concrete action: registering, saving, and kicking off DNS/deliverability verification. It explicitly distinguishes itself from check_domain and list_domains, so an agent can route correctly without opening any 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?

Contains explicit 'USE THIS when...' guidance for the intended scenario and two 'DO NOT use...' exclusions naming the correct alternative for each (check_domain for testing an external/unverified domain, list_domains for listing). Nothing is left to inference.

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