IntoDNS.ai DNS & Email Security Scanner

Start deep scan

start_deep_scan

Start a long-running Internet.nl deep scan. Internet.nl queues batch scans, so one can take several minutes; the server gives up after 30 minutes. Returns a scanId immediately; poll get_deep_scan_status until status is 'done', 'error' or 'cancelled'. Every call starts a new scan, so do not repeat a call that succeeded. Does not modify the domain: it only reads its public DNS, web and mail endpoints. Internet.nl runs an exhaustive standards-compliance audit (IPv6, DNSSEC, modern TLS, RPKI, mail authentication) used by EU governments. Use when scan_domain output is not strict enough for compliance reporting, or when the user asks for an Internet.nl-grade audit. For sub-10s answers, use scan_domain. To abort an in-progress scan, call cancel_deep_scan. No auth.

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

Input Schema

Name	Required	Description	Default
`name`	No	Optional display name
`domain`	Yes	Domain name only, e.g. example.com (no URL, path, or port)
`scanType`	No	Deep scan type	both

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: scans queue and can take minutes, the server times out after 30 minutes, a scanId is returned immediately, and every call starts a new scan despite non-idempotent annotations. It also clarifies that the domain itself is not modified, which helps reconcile the non-read-only server state with the read-only effect on the target domain.

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?

The description is front-loaded with the core action and timing behavior, then proceeds to polling, idempotency, side effects, and alternatives. Every sentence provides useful operational or routing information without redundancy.

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?

Although there is no output schema, the description explains the immediate return value (scanId) and the required polling flow with terminal statuses. It also covers timeout behavior, non-idempotency, side effects, and alternatives, which is complete for this long-running scan tool.

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, name, and scanType parameters are already documented in the input schema. The description does not add meaningful semantics about the parameters beyond what the schema provides, so the baseline score 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?

The description states a specific verb and resource: start a long-running Internet.nl deep scan. It clearly distinguishes this from the sibling scan_domain by naming both and explaining the compliance-audit depth difference.

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?

It gives explicit when-to-use guidance: scan_domain output is insufficient for compliance reporting or the user requests an Internet.nl-grade audit. It also names alternatives for fast answers (scan_domain) and abortion (cancel_deep_scan), and explains polling via get_deep_scan_status.

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

All IntoDNS.ai DNS & Email Security Scanner 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.