Skip to main content
Glama
Sign In

Groundmail

by io.github.Groundmail
OverviewDiscussionsAdmin

Apply domain DNS records

apply_domain_dns
DestructiveIdempotent

Apply Groundmail DNS records for a domain through Cloudflare, Vercel, GoDaddy, Netlify, DigitalOcean or DNSimple, using the provider account connected in the dashboard. If none is connected, ask the user to connect it at https://app.groundmail.dev/integrations (never ask for the provider token in chat), or have them publish the records from create_domain by hand.

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name or id of a domain already added to this account (example.com)
providerYesDNS provider that hosts the domain

Output Schema

NameRequiredDescriptionDefault
domainYesDomain the records belong to
recordsNoDNS records to publish for the domain
resultsYesOutcome for each record
providerYesDNS provider the records were written to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / records / items / properties / already_set
      Added value: +{
+  "description": "True when the domain already publishes a record that does this job (its own DMARC record). The value is what is there now: nothing to add or change, never publish a second one",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / provider / enum
      Previous value: -[
-  "cloudflare",
-  "godaddy",
-  "vercel"
-]New value: +[
+  "cloudflare",
+  "godaddy",
+  "vercel",
+  "netlify",
+  "digitalocean",
+  "dnsimple"
+]
  3. Changed1 schema field changed
    • removedInput schema / properties / credentials
      Removed value: -{
-  "description": "Optional one-time credentials: Cloudflare apiToken (and zoneId), Vercel apiToken (and teamId), or GoDaddy apiKey and apiSecret",
-  "type": "object"
-}
  4. Changed1 schema field changed
    • changedInput schema / properties / credentials / description
      Previous value: -"Optional inline registrar credentials (GoDaddy api key/secret)"New value: +"Optional one-time credentials: Cloudflare apiToken (and zoneId), Vercel apiToken (and teamId), or GoDaddy apiKey and apiSecret"
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare mutation, destructiveness, idempotency, and open-world behavior. The description adds important operational context beyond annotations: the dashboard-connected provider requirement, the setup URL, the token-handling constraint, and the manual fallback.

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?

The action and provider scope are front-loaded, followed by the fallback path and safety warning. Every sentence adds operational value, and there is no redundant restatement of schema or annotations.

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?

For a destructive mutation with annotations and an output schema, the description covers the key missing human-facing context: connected provider prerequisite, fallback instructions, and token safety. Return values need not be explained because an output schema exists.

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 in the input schema. The description reinforces the provider list and domain context but does not add syntax or format details beyond what the schema provides.

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?

The description states a specific verb and resource: apply Groundmail DNS records for a domain through named DNS providers. It distinguishes the action from create_domain by positioning create_domain as the manual alternative, so an agent can identify the tool's role without opening sibling 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?

It explicitly covers the prerequisite scenario: use the provider account connected in the dashboard. If none is connected, it directs the agent to ask the user to connect at a specific URL or publish records manually via create_domain, and it warns never to ask for the provider token in chat.

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

All Groundmail toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources