Skip to main content
Glama
agentisend

agentisend

Domain DNS setup sheet

setup_domain
Idempotent

Get the one-shot DNS sheet for a registered domain: zone file, copy-paste commands for Cloudflare, Route 53 and gcloud, plus every record to publish with its action.

Instructions

Purpose: get the one-shot DNS sheet for a domain already registered with create_domain — zone file, copy-paste commands, provider, and every record with host, value_strings and whether it is required. NOT for: registering the domain (create_domain) or re-checking DNS (verify_domain / wait_for_domain). Returns: zone_file (required records first), commands for Cloudflare, Route 53 and gcloud, provider_hints, and the records to publish. Each record says action: add, edit (an SPF or DMARC record is already there — change it to value, never add a second), none (already in place) or check (what is there could not be read; see note). Pass the domain id or the domain name as domain. name means the same thing.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain id from create_domain, or the domain name. name is an alias for this argument.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
recordsNo
commandsNoCopy-paste commands for common DNS providers.
zone_fileNoThe records as a zone file, required ones first.
provider_hintsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: each record carries an action (add/edit/none/check) with the meaning of each, and an explicit warning that an existing SPF/DMARC record must be edited rather than added a second time. It does not explain the side effect implied by readOnlyHint=false with idempotentHint=true, which leaves the tool's write behavior unexplained for a non-read-only operation.

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-loads Purpose, then NOT for, then Returns, which is a usable structure for scanning. It is a dense single paragraph, but nearly every clause (record actions, provider list, SPF/DMARC caveat) carries information rather than filler.

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?

Covers purpose, exclusions, prerequisites, accepted identifier forms, and even summarizes the return shape despite an output schema existing. For a two-parameter tool with full schema coverage and an output schema, nothing needed to call it correctly is missing.

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 description coverage is 100%, so both parameters are already documented, including the 'name is an alias' note the description repeats. The description's added value here is minimal (restating that id or name is accepted), so the baseline 3 applies.

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 ('get the one-shot DNS sheet for a domain') plus the scope of what the sheet contains (zone file, commands, provider, records). It explicitly names the siblings it is not (create_domain, verify_domain, wait_for_domain), so an agent can distinguish it without opening another 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?

Provides an explicit 'NOT for' clause with the alternative tools named for each excluded use, and states the precondition that the domain must already be registered via create_domain. Nothing about when to select this tool 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.