Skip to main content
Glama

Add domain

add_domain

Add a sending domain to the account. Returns the DNS records that must be added at the domain registrar (ownership TXT, SPF, DKIM, return path).

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

NameRequiredDescriptionDefault
domainYesDomain name, for example example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the mutation and external-dependency profile is covered. The description adds genuine value by stating the tool returns the DNS records the caller must install, which is behavioral context not in the annotations. It stops short of disclosing idempotency or the verify_domain follow-up required before the domain can send.

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?

Two sentences, zero filler, with the action front-loaded and the return payload second. Every clause carries information the caller 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 creation tool with annotations supplied and no output schema, the description covers the action and the response shape, which is the main thing an agent must know. The remaining gap is workflow context: nothing says the domain is unusable until the DNS records are verified.

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% with a single documented 'domain' property, so the schema carries the parameter meaning and the baseline is 3. The description adds only the qualifier 'sending domain', which conveys no format, normalization, or subdomain-handling rules beyond the schema example.

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 names a specific verb and resource ('Add a sending domain to the account') and even previews the return payload (DNS records: ownership TXT, SPF, DKIM, return path). That is enough to separate it from add_route, add_webhook, and get_domain without opening a schema, though no sibling is named explicitly.

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?

Usage is only implied: the agent can infer you add a domain before it can send mail, and that DNS records must be configured at the registrar. There is no statement about when to prefer this over alternatives, no prerequisite (e.g., the domain must subsequently be verified with verify_domain), and no note on what happens if the domain already exists.

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