Skip to main content
Glama

Verify sending domain

domain_verify
Idempotent

Re-checks the DNS records for a sending domain now and returns, per record, whether it was found plus expected vs actual values. Uses no quota, changes nothing, safe to repeat. DNS changes can take minutes to a few hours to show up; if records are missing right after adding them, wait a bit and try again. Explain any wrong record in plain words. Requires API key scope: account.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA sending domain or subdomain, for example mail.example.com. No https://, no path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds real behavioral facts beyond the structured hints: no quota consumed, nothing mutated, safe to repeat, and a realistic DNS propagation window of minutes to hours with retry advice. This is exactly the operational context annotations cannot convey. The only tension is 'changes nothing' against readOnlyHint=false, but that hint asserts the absence of a guarantee rather than asserting mutation, so it reads as the annotation being conservative rather than the description being wrong.

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-loaded with the action and the return shape, then the cost/safety facts, then the propagation caveat. Every clause contributes. Slightly dense in the middle, and the closing 'explain any wrong record in plain words' is an output-style instruction rather than tool behaviour, but nothing is 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?

With one parameter, no output schema and no nesting, this is fully sufficient: it names what comes back (found flag plus expected vs actual per record), guarantees no side effects or quota cost, and explains the common false-negative of premature checking. An agent can call it and interpret the result without further information.

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 the single domain parameter is documented with format, length bounds and an example in the schema itself. The description adds no extra constraint on the domain argument, so it neither compensates for nor exceeds what the schema already provides — baseline 3.

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 — re-checks DNS records for a sending domain — and specifies scope ('now') and return shape ('per record, whether it was found plus expected vs actual values'). This is clearly distinguishable from domain_add (which would set up the domain) and domain_list, so an agent can pick it without opening the schema.

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?

Gives a concrete trigger condition: records missing right after adding them means DNS hasn't propagated, so wait and retry. That implies the sequence add-then-verify without naming a sibling explicitly. It stops short of stating when NOT to use it (e.g. before the domain exists), so it is strong context rather than a full routing rule.

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