Leadgen ONRC Romania

Domain WHOIS, DNS and email audit

lookup_domain

Read-onlyIdempotent

WHOIS plus DNS records (A, MX, NS, TXT) and an SPF/DMARC email-security audit for a domain. Use it to profile a company's web estate or check its email posture. include_dns and include_security toggle the two halves.

Input Schema

TableJSON Schema

Name	Required	Description
`domain`	Yes	Domain name to look up (e.g. 'example.com'); a URL is reduced to its host.
`include_dns`	No	Include DNS records (A, AAAA, MX, NS, TXT, SOA); default true.
`include_security`	No	Include the SPF/DMARC email-security check; default true.

Output Schema

TableJSON Schema

Name	Required	Description
`dns`	No	Records by type: A, AAAA, MX, NS, TXT, SOA.
`error`	No	Set only when there is no answer (empty_query, invalid_cui, data_unavailable, plan_required ...); such a call is not counted.
`whois`	No	registrar, creationDate, expirationDate, updatedDate, nameServers, registrantOrg, registrantCountry.
`domain`	No	The normalised domain.
`message`	No	A sentence for the caller.
`security`	No	hasSPF, spf, hasDMARC, dmarc.
`resolvedIP`	No	An address the domain resolves to.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 17, 2026

addedInput schema / properties / domain / description

Added value: +"Domain name to look up (e.g. 'example.com'); a URL is reduced to its host."

addedInput schema / properties / include_dns / description

Added value: +"Include DNS records (A, AAAA, MX, NS, TXT, SOA); default true."

addedInput schema / properties / include_security / description

Added value: +"Include the SPF/DMARC email-security check; default true."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "WHOIS, DNS records and the SPF/DMARC audit of a domain.",
+  "properties": {
+    "dns": {
+      "description": "Records by type: A, AAAA, MX, NS, TXT, SOA.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "domain": {
+      "description": "The normalised domain.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Set only when there is no answer (empty_query, invalid_cui, data_unavailable, plan_required ...); such a call is not counted.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "description": "A sentence for the caller.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "resolvedIP": {
+      "description": "An address the domain resolves to.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "security": {
+      "description": "hasSPF, spf, hasDMARC, dmarc.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "whois": {
+      "description": "registrar, creationDate, expirationDate, updatedDate, nameServers, registrantOrg, registrantCountry.",
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 8, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare this a read-only, idempotent, open-world, non-destructive operation, so the safety profile is covered. The description adds that the lookup is split into DNS and email-security halves, but discloses nothing about rate limits, failures on non-existent domains, or external source variability that an agent would find useful.

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?

Three tight sentences with the payload list front-loaded and the toggles noted last. Nothing is padded, though the final toggle sentence is largely redundant with the schema.

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?

An output schema exists, so return values need no explanation here, and the description covers scope, toggles, and intended use. A note on behavior for non-existent or malformed domains would complete it, but it is otherwise sufficient for correct invocation.

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%, so all three parameters are fully documented in the schema, including defaults and the URL-to-host normalization. The description's note that include_dns/include_security toggle the two halves restates what the schema already conveys, so the baseline 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 (lookup) and resource (domain) and enumerates the concrete payloads: WHOIS, DNS records, and an SPF/DMARC email audit. This distinguishes it from the sibling company-lookup tools, which fetch entity data rather than domain infrastructure.

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?

"Use it to profile a company's web estate or check its email posture" gives clear context for when to reach for this tool. It stops short of naming an alternative or exclusion (e.g., when to prefer find_company_by_domain or enrich_company instead), so it is not a full when/when-not statement.

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

All Leadgen ONRC Romania 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.