Skip to main content
Glama
agentisend

agentisend

Re-check a domain's DNS records

verify_domain
Idempotent

Re-checks a domain's public DNS records and reports which required records are present, showing pending status while propagation completes rather than treating it as a failure.

Instructions

Purpose: re-read the public DNS for a domain and report which records are in place. NOT for: creating records. Publishing DNS is done wherever the domain is hosted, by whoever runs it. Returns: the same domain view GET /domains/:id returns after the check — every record with status, host, value_strings, required and observed. A domain with nothing published yet stays pending rather than failing: DNS takes minutes to a day or two to spread, and calling that a failure would make you give up on a domain that is about to work. Pass the domain id or the domain name as domain_id. id and name mean the same thing.

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
domain_idYesThe domain id or the domain name. name is an alias for this argument.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
idNoIdentifier.
nameNo
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
regionNo
statusNopending, verified, failed or temporary_failure.
recordsNoEach DNS record with its status.
tls_modeNoopportunistic or enforced.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With readOnlyHint=false and openWorldHint=true already declared, the description adds real behavioral context: the check reaches out to public DNS, and an unpublished domain stays 'pending' rather than failing because propagation takes minutes to days. That pending-vs-failure rule is the key non-obvious behavior and is not inferable from annotations. It doesn't, however, explain why the call is flagged as a non-read-only operation.

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?

Front-loaded and segmented into Purpose / NOT for / Returns, so an agent can scan the exclusion and the return semantics immediately. Every sentence carries information — even the propagation-delay rationale justifies the pending behavior rather than padding.

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 two-parameter verification tool with an output schema, the description covers purpose, the excluded use case, the alias handling, and the pending-vs-failure outcome. Since an output schema exists, it does not need to enumerate return fields, and it correctly leaves them to the schema.

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, including the id/name alias. The description repeats the alias ('Pass the domain id or the domain name as domain_id. id and name mean the same thing') without adding syntax or constraints beyond the schema. Baseline 3 for a fully-covered schema.

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: 're-read the public DNS for a domain and report which records are in place.' The 're-read' framing distinguishes it from a passive read (get_domain) and from provisioning (setup_domain/create_domain), and the explicit 'NOT for: creating records' rules out the main confusion.

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 negative condition ('NOT for creating records; publishing is done wherever the domain is hosted') and explains the pending-tolerance so the agent doesn't treat slow propagation as failure. It never names the closest alternatives (get_domain, wait_for_domain) as routing options, so it stops short of full when-to-use guidance.

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