Ranla

Verify domain

verify_domain

Idempotent

Verify DNS for a sending domain after records are applied.

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain id or name (example.com)

Output Schema

Name	Required	Description
`auto`	No
`checks`	No
`domain`	Yes
`records`	No	Sending DNS records to add at the DNS provider
`analysis`	No	DMARC and BIMI findings for the domain
`verified`	Yes	True once DNS checks out. A domain whose DNS is not ready comes back as an error instead.
`inbound_note`	No
`tracking_dns`	No	The tracking record, when tracking is on
`inbound_error`	No
`signing_ready`	No	True when the mail server can sign mail for the domain
`inbound_pending`	No
`inbound_records`	No	Records for inbound receiving
`inbound_configured`	No
`mail_server_signing`	No
`mail_server_registered`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

addedInput schema / properties / domain / description
```
Added value: +"Domain id or name (example.com)"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "analysis": {
+      "additionalProperties": true,
+      "description": "DMARC and BIMI findings for the domain",
+      "type": "object"
+    },
+    "auto": {
+      "type": "boolean"
+    },
+    "checks": {
+      "properties": {
+        "dkim": {
+          "type": "boolean"
+        },
+        "dmarc": {
+          "type": "boolean"
+        },
+        "ownership": {
+          "type": "boolean"
+        },
+        "return_path": {
+          "type": "boolean"
+        },
+        "spf": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "domain": {
+      "properties": {
+        "click_tracking": {
+          "type": "boolean"
+        },
+        "created_at": {
+          "description": "ISO 8601",
+          "type": "string"
+        },
+        "id": {
+          "description": "Domain id",
+          "type": "string"
+        },
+        "inbound_enabled": {
+          "type": "boolean"
+        },
+        "inbound_error": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "inbound_status": {
+          "description": "disabled, pending, active, or error",
+          "type": "string"
+        },
+        "name": {
+          "description": "Domain name",
+          "type": "string"
+        },
+        "open_tracking": {
+          "type": "boolean"
+        },
+        "status": {
+          "description": "Verification status",
+          "type": "string"
+        },
+        "tls_mode": {
+          "type": "string"
+        },
+        "verified_at": {
+          "description": "ISO 8601",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "id",
+        "name"
+      ],
+      "type": "object"
+    },
+    "inbound_configured": {
+      "type": "boolean"
+    },
+    "inbound_error": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "inbound_note": {
+      "type": "string"
+    },
+    "inbound_pending": {
+      "type": "boolean"
+    },
+    "inbound_records": {
+      "description": "Records for inbound receiving",
+      "items": {
+        "properties": {
+          "host": {
+            "type": "string"
+          },
+          "priority": {
+            "description": "MX preference",
+            "type": "number"
+          },
+          "purpose": {
+            "description": "What the record is for, e.g. spf, dkim, dmarc",
+            "type": "string"
+          },
+          "type": {
+            "description": "Record type: TXT, CNAME, MX…",
+            "type": "string"
+          },
+          "value": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "host",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "mail_server_registered": {
+      "type": "boolean"
+    },
+    "mail_server_signing": {
+      "properties": {
+        "dkim_ok": {
+          "type": "boolean"
+        },
+        "dkim_status": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "return_path_ok": {
+          "type": "boolean"
+        },
+        "return_path_status": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "records": {
+      "description": "Sending DNS records to add at the DNS provider",
+      "items": {
+        "properties": {
+          "host": {
+            "type": "string"
+          },
+          "priority": {
+            "description": "MX preference",
+            "type": "number"
+          },
+          "purpose": {
+            "description": "What the record is for, e.g. spf, dkim, dmarc",
+            "type": "string"
+          },
+          "type": {
+            "description": "Record type: TXT, CNAME, MX…",
+            "type": "string"
+          },
+          "value": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "host",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "signing_ready": {
+      "description": "True when the mail server can sign mail for the domain",
+      "type": "boolean"
+    },
+    "tracking_dns": {
+      "description": "The tracking record, when tracking is on",
+      "properties": {
+        "host": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ok": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "required": {
+          "description": "True when open or click tracking needs its own record",
+          "type": "boolean"
+        },
+        "target": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "verified": {
+      "description": "True once DNS checks out. A domain whose DNS is not ready comes back as an error instead.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "domain",
+    "verified"
+  ],
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the sequencing constraint; it says nothing about what state changes on success/failure, how long propagation takes, or whether the check is synchronous, which are the behaviors an agent actually needs here.

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?

One sentence, front-loaded with the action and resource, and every clause (DNS, sending domain, after records applied) carries information. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and the single parameter is fully documented. However, for a DNS verification tool the description omits practically relevant context such as propagation delay, expected failure modes, or whether re-verification is safe to repeat.

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 as an id-or-name, so the schema carries the load. The description adds no format or syntax detail beyond that, which is the expected baseline when the schema is complete.

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?

States a specific verb ('Verify') plus the resource and scope ('DNS for a sending domain'), which is more precise than the bare title. It is distinguishable from the adjacent write tool apply_domain_dns, though it never names it or any sibling explicitly.

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?

'after records are applied' supplies a clear prerequisite/sequencing cue relative to apply_domain_dns, but there are no explicit when-not conditions, no mention of retry cadence, and no named alternative. Usage is implied rather than stated.

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

All Ranla tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?