Skip to main content
Glama

Add sending domain

domain_add
Idempotent

Adds a sending domain (one per workspace) and returns the exact DNS records to create, plus registrar_hint (cloudflare, godaddy, namecheap, route53, vercel or unknown). Uses no quota. Safe to call again: an existing domain returns its current records. If you have a DNS provider tool for that registrar connected, offer to add the records yourself; otherwise show them as a table and point the person to their DNS settings or the Hollerpost dashboard. Then call domain_verify. Requires API key scope: account.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA sending domain or subdomain, for example mail.example.com. No https://, no path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that no quota is consumed, that the call is idempotent in effect (existing domain returns current records), and that it requires the 'account' API key scope. The annotations already declare idempotentHint and destructiveHint=false, and the description reinforces rather than contradicts them.

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?

Front-loads the action and return value, then layers the idempotency note, the registrar branching, and the scope requirement. Every sentence carries operational information; nothing is redundant with the title or schema.

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 compensates by naming the return payload (exact DNS records plus registrar_hint with its possible values). For a one-parameter tool with full schema coverage, an agent has everything needed to call it and act on the result.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter's format (no https://, no path, example subdomain) is fully documented in the schema. The description adds the meaningful constraint that only one domain per workspace is allowed, which the schema cannot express, though it adds nothing further about the domain string itself.

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 and resource ('Adds a sending domain') plus the cardinality constraint (one per workspace) and what it returns (DNS records and registrar_hint). It also names the follow-up sibling domain_verify, so an agent can place it in the workflow without opening the 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?

Explicitly covers when to call it, that it is safe to re-call because an existing domain returns its current records, and the branching next step: use a connected DNS provider tool if available, otherwise present records as a table and point to DNS settings or the dashboard, then call domain_verify. Both the alternative path and the required successor are named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources