Skip to main content
Glama

Send domain confirmation again

domainVerificationResend

Ask the registrar to resend its confirmation email for a domain Tofu registered for this signed-in account. The input is the domain name, not a projectId or email address. Uses the registrar’s pending verification for this owned domain, the account’s existing allowance and the registrar’s 15-minute throttle. sent means an email was sent to the registrant; not_needed means no pending confirmation; wait gives the next eligible time when known; unsure means the registrar did not confirm sending; the sending outcome is uncertain and the registrar’s throttle still applies. Returns no contact address or transfer code. The registrant confirms through the link in the email before the verification deadline; this tool only requests the email.

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

Input Schema

NameRequiredDescriptionDefault
domainYes

Output Schema

NameRequiredDescriptionDefault
messageYes
outcomeYes
nextEligibleAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag a non-read-only, non-idempotent, open-world side effect, and the description adds a lot beyond them: the 15-minute registrar throttle, the account allowance, the four outcome states with their meanings, and the explicit note that no contact address or transfer code is returned. The throttle and outcome explanations are exactly the extra context annotations cannot convey; only the 'unsure' sentence is muddled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and the input constraint, which is good, but the outcome glossary turns into a run-on where 'unsure' is defined twice in succession ('the registrar did not confirm sending; the sending outcome is uncertain and the registrar's throttle still applies'). It is dense rather than tight; the throttle is mentioned twice and could be stated once.

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?

Although an output schema exists, the description still summarizes the outcome vocabulary and explicitly says what is not returned (no contact address, no transfer code), which pre-empts likely agent speculation. Combined with the deadline note and the throttle, an agent has everything needed to call this correctly and to interpret the result.

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 0%, so the description carries the burden; it does add real meaning by saying 'The input is the domain name, not a projectId or email address' and by tying the value to a domain owned by the signed-in account. Beyond that it adds no format, case, or normalization detail that the regex pattern would not already enforce, so it compensates only partially.

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 ('Ask the registrar to resend its confirmation email') and scopes it to domains 'Tofu registered for this signed-in account'. It also draws the boundary against the obvious alternative by saying this tool 'only requests the email' while 'the registrant confirms through the link', so an agent can tell it apart from a verify/confirm tool without opening a 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 clear context for use (there is a pending registrar verification on an owned domain, subject to the account allowance and a 15-minute throttle) and the outcome values implicitly tell the agent what happens when it is called too early ('not_needed', 'wait'). It never names an alternative sibling to use instead, nor states prerequisites such as the domain needing to be owned, so it stops short of explicit when/when-not guidance.

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