Skip to main content
Glama
agentisend

agentisend

Wait for a domain to verify

wait_for_domain
Read-onlyIdempotent

Waits until a sending domain is verified or failed, letting you track DNS verification without rechecking it yourself; use timeout=0 for a snapshot.

Instructions

Purpose: wait until a sending domain is verified or failed, without re-checking DNS yourself. Pass the id or the domain name as domain (name means the same thing). timeout=0 is a snapshot of the last check. NOT for: publishing DNS, or forcing a new lookup (verify_domain). The server keeps checking on its own for 72 hours. Returns: status, next_poll_seconds (when the server will check again), deadline (when the 72-hour window closes), reason, and progress (required_verified of required_total). If it is still pending, call again after next_poll_seconds, or send to an address ending in @simulator.agentisend.com meanwhile.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain id from create_domain, or the domain name. name is an alias for this argument.
timeoutNoSeconds to wait, 0–25. 0 returns the last stored check immediately.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
reasonNo
statusNo
deadlineNoWhen the 72-hour window closes.
progressNorequired_verified of required_total.
next_poll_secondsNoWhen the server checks again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish this as a safe, idempotent read, and the description adds real behavior beyond them: the server keeps checking on its own for 72 hours, timeout=0 returns a stored snapshot rather than triggering a lookup, and progress tracking via required_verified/required_total is disclosed. That is meaningful async semantics not derivable from the annotations.

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?

The Purpose / NOT for / Returns structure is front-loaded and scannable, and every sentence carries routing or behavioral information. The Returns enumeration is slightly redundant against the existing output schema, which keeps it from a 5.

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 polling tool with a 72-hour deadline, the description supplies the retry cadence, the deadline meaning, and a fallback path for testing. Although an output schema exists, the added asynchronous context is what makes the tool callable correctly in a loop.

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 the domain alias and the 0–25 timeout semantics are already documented in the schema. The description restates that id or name is accepted and that timeout=0 is a snapshot, adding little beyond the schema, so the baseline of 3 applies.

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+resource (wait until a sending domain is verified or failed) with the explicit scope 'without re-checking DNS yourself'. It clearly separates itself from get_domain and verify_domain, so an agent can route correctly 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 Guidelines5/5

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

The 'NOT for: publishing DNS, or forcing a new lookup (verify_domain)' line names the alternative and the excluded action outright. It also gives positive routing guidance ('call again after next_poll_seconds'), which is exactly the when-to-use information an agent needs.

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