Skip to main content
Glama
Sign In

Nextmail

by sh.nextmail
OverviewDiscussionsAdmin

Set domain DNS zone

setDomainDnsZone
Destructive

Choose the zone of a connected DNS account that a domain is set up through, when several could answer for it. The zone has to cover the domain, be active and take a test record. Nothing is written yet: syncDomainDns writes the records.

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>",
      "connection": "<connection>",
      "zone": "<zone>"
    },
    "name": "setDomainDnsZone"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneYesThe id of the zone, as getDomainDns lists the zones that could answer for the domain.
domainYesThe domain, by its id or by its name (example.com). listDomains names every one.
connectionYesThe id of a DNS connection, as listDnsConnections names it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds real context beyond the annotations: the prerequisites for a valid zone and the fact that no DNS records are written at this step. The 'nothing is written yet' phrasing sits in mild tension with destructiveHint=true / readOnlyHint=false, but the sentence clarifies it concerns DNS records rather than the config change, so it reads as clarification rather than contradiction.

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?

Three short sentences, front-loaded with the purpose and eligibility, then the write-is-later caveat. No redundant restatement of the title or schema.

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?

Given annotations cover the mutation/safety profile and all three params are fully described in schema, the description supplies the missing decision context (when to use, eligibility, follow-up write step). Minor gap: it doesn't note what happens to any previously selected zone when overwritten.

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 each parameter is documented with pointer tools (getDomainDns, listDomains, listDnsConnections). The description adds eligibility meaning for the zone but says nothing new about domain or connection 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?

Specific verb (choose/set) and resource (the zone for a domain on a DNS connection), with scope narrowed to the case where several zones could answer. It explicitly distances itself from syncDomainDns, so an agent can tell the two apart without opening schemas.

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?

States the trigger condition (multiple candidate zones) and the eligibility requirements (zone must cover the domain, be active, accept a test record). It also names the alternative that performs the write (syncDomainDns), giving explicit use/not-use routing.

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

All Nextmail toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources