IntoDNS.ai DNS & Email Security Scanner

Full domain report

get_everything_report

Read-onlyIdempotent

Generate the complete live IntoDNS.ai report covering DNS, email authentication, web/HTTPS, blacklist reputation, sender requirements, and canonical citation URLs in a single call. Read-only, no domain mutation. ~5-15s latency depending on backend cache state. Use when the user asks for everything, the full picture, or a deep current-state summary; use scan_domain for a faster default scan, or create_report_snapshot when the result must remain immutable for audit/ticket use. No auth, no side effects.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain name only, e.g. example.com (no URL, path, or port)
`format`	No	Return JSON data or LLM-ready Markdown	json

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds genuinely new operational context beyond annotations: ~5-15s latency that varies with backend cache state, and no auth requirement. The 'Read-only, no domain mutation' and 'no side effects' clauses partly restate readOnlyHint/destructiveHint, but the latency and cache-variance warning is material for an agent deciding whether to call a broad report tool.

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?

Front-loaded and dense: purpose first, then mutation profile, latency, and alternative routing in a logical order. Slight redundancy in stating 'Read-only, no domain mutation' and then 'No auth, no side effects' at the tail, which repeats the safety message already delivered up front.

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?

For a broad aggregate-report tool with no output schema, the description still tells the agent what sections the result contains (including canonical citation URLs), how long it takes, and which sibling to pick for speed or immutability. Nothing an agent needs to select or invoke it correctly is missing.

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 both parameters (domain, format enum) are fully documented in the schema, so the schema carries the load. The description adds no extra detail about domain formatting or when markdown output is preferable, which is the baseline 3 case.

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 (generate) and a precisely scoped resource (complete live IntoDNS.ai report), then enumerates the covered surfaces: DNS, email auth, HTTPS, blacklist, sender requirements, citations. This makes it unmistakable versus siblings like check_spf or scan_domain which cover single facets.

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?

Explicit routing guidance: use when the user asks for 'everything' or a 'deep current-state summary', with two named alternatives and the condition that selects each (scan_domain for a faster default, create_report_snapshot when the result must be immutable for audit/ticket use). No inference required.

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.