Skip to main content
Glama
Sign In

Mailercloud

by io.github.mailercloud-com
OverviewDiscussionsAdmin

Verify Domain

verify_domain
Idempotent

Re-check a sending domain's DNS records now and return each record's status and the fix for any that is wrong. Run it after the user has published the records from add_domain. Needs domain_id.

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_id": "<domain_id>"
    },
    "name": "verify_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoShow which domain would be checked without checking it
domain_idYesDomain ID (from list_domains or add_domain)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare idempotent, non-destructive and open-world, but don't convey that this initiates a fresh live DNS lookup rather than reading cached state; 'Re-check ... now' adds exactly that. It omits DNS propagation lag and any throttling on repeated checks, which matters for a verify tool.

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, front-loaded with the action and payoff, then the prerequisite. Nothing is padded or redundant.

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?

With no output schema, the description correctly summarizes the return value (per-record status and fixes), and it states the prerequisite. The unmentioned dry_run option is the only loose end for a two-parameter tool.

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 both domain_id and dry_run documented in the schema itself. The description's 'Needs domain_id' restates the required flag and never mentions dry_run, so it adds no meaning beyond structured data.

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 gives a specific verb and resource ('Re-check a sending domain's DNS records now'), states what comes back (each record's status plus the fix for wrong ones), and positions it against the sibling add_domain as the follow-up step rather than a duplicate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The timing is explicit: run it after the user has published the records from add_domain. It does not mention when to prefer get_domain or check_sending_setup, so the alternative-selection guidance stops short of a full 5.

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

All Mailercloud toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources