Skip to main content
Glama

Verify domain

domainVerify
Idempotent

Check a connected hostname’s DNS records and continue its connection — Check now on the Domains page: Tofu re-reads the ownership TXT challenge, verifies the hostname with the hosting provider and reports the new status. next.step says what it waits on and next.waitingOn who acts; at live the app answers at the hostname over HTTPS, and allow_certificate on a connected connection means it answers now but its certificate cannot renew until the human adds the CAA records. On a connected root or www, message may say where the other name stands: next never waits on that name’s record (in dnsRecords; Tofu writes it where it runs a bought domain’s DNS for this app), and only connecting it on its own moves it here from another hosting account. Safe to repeat while records propagate; DNS propagation may remain pending between checks. It cannot create or transfer a domain, it never buys one, and it never touches records that belong to somebody else.

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": {
      "projectId": "<projectId>",
      "domainId": "<domainId>"
    },
    "name": "domainVerify"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainIdYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With readOnlyHint=false and idempotentHint=true already supplied, the description still adds real behavior: it re-reads the ownership TXT challenge, verifies with the hosting provider, and reports a new status; it may write a DNS record where Tofu runs the app's DNS; and allow_certificate on a connected connection signals cert renewal is blocked until CAA records are added. The only thing weighing against a 5 is how much of the disclosure is spent restating return-field semantics rather than action behavior.

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?

Purpose is front-loaded in the first clause, which is good, but the body is one long run-on paragraph dense with backticked jargon ('next.step', 'next.waitingOn', 'dnsRecords', 'allow_certificate') where the parenthetical about dnsRecords is hard to parse. The content earns most of its place, but the structure makes it harder to scan than it needs to be.

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?

Since an output schema exists, the description does not owe the agent full return-value documentation, yet it covers side effects, repeat-safety, propagation timing, and the certificate/CAA caveat. What it lacks is parameter-level grounding for a 2-required-param tool, which is the one real completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both required parameters (projectId, domainId) have 0% schema description coverage, so the description needed to define them and instead says nothing about either. It refers loosely to 'a connected hostname' and 'its connection' but never grounds that in the domainId/projectId pair, leaving the agent to infer the identifier requirements.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Check a connected hostname's DNS records and continue its connection.' It also carves out scope ('cannot create or transfer a domain, never buys one, never touches records that belong to somebody else'), which separates it from domainConnect and domainAuthorize. It stops short of naming a sibling by name, but an agent can tell what the tool does.

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

Usage Guidelines3/5

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

It says the check is 'safe to repeat while records propagate' and that propagation may remain pending between checks, which implies polling usage. What is missing is explicit routing to alternatives: it never says when to use domainVerificationResend instead of re-checking, or when domainConnect is the required precursor. Usage is implied, not prescribed.

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