Skip to main content
Glama
RoscoNL

intodns-mcp

by RoscoNL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

start_deep_scan

Start a deep Internet.nl scan for domain compliance (IPv6, DNSSEC, TLS, mail auth). Returns scanId to poll until complete.

Instructions

Start a long-running Internet.nl deep scan (typically 30-120s). Returns a scanId immediately; poll get_deep_scan_status until status='finished'. Read-only — no domain mutation. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional display name
domainYesDomain name only, e.g. example.com (no URL, path, or port)
scanTypeNoDeep scan typeboth

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name, e.g. example.com"New value: +"Domain name only, e.g. example.com (no URL, path, or port)"
    • addedInput schema / properties / domain / maxLength
      Added value: +253
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior1/5

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

The description claims 'Read-only — no domain mutation' while the annotations set readOnlyHint=false, which is a direct contradiction. The description also does not disclose other behavioral aspects like side effects or long-running nature beyond what the annotation hints suggest.

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?

The description is clear and organized but contains some redundancy (e.g., 'Internet.nl' repeated, 'scan_domain' mentioned twice). It remains concise and focused without unnecessary bulk.

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?

Given there is no output schema, the description appropriately explains that a scanId is returned immediately and that polling via get_deep_scan_status is required. It also names cancel_deep_scan for aborts. However, it omits mention of error handling or rate limits, which would improve completeness.

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 descriptions cover all three parameters (domain, scanType, name) with adequate detail. The description does not add extra semantics beyond the schema, 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 clearly states the tool starts a long-running deep scan and distinguishes it from the faster scan_domain tool. It specifies the verb 'start' and the resource 'deep scan', making the purpose unambiguous.

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?

The description explicitly states when to use this tool (when scan_domain output is not strict enough or when an Internet.nl-grade audit is needed) and when to use the alternative (scan_domain for sub-10s answers). It provides clear usage criteria.

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

Deploy Server

Other Tools