IntoDNS.ai DNS & Email Security Scanner

Create report snapshot

create_report_snapshot

Create an immutable evidence snapshot of the current Everything Report for a domain. Returns a snapshot ID, ISO timestamp, SHA-256 content hash, and stable bookmarkable URLs for both JSON and Markdown renderings of the report. Snapshots are write-once and resolve to the same evidence months/years later — useful for tickets, audit trails, NIS2/ISO compliance evidence, and LLM citations that should not drift. A canonical POST creates one snapshot per call (additive and not idempotent); use get_report_snapshot to read it back. Use this instead of get_everything_report when the result must remain stable.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain name only, e.g. example.com (no URL, path, or port)
`format`	No	Return the created snapshot as JSON or Markdown	json

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnly/idempotent/destructive booleans; the description adds the semantics behind them — write-once immutability, one snapshot per call, additive and not idempotent, and that snapshots remain resolvable months/years later. It also discloses the return payload (snapshot ID, ISO timestamp, SHA-256 hash, JSON/Markdown URLs), which annotations cannot convey. No contradictions with the hints.

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 with the action and the return contract, then the durability rationale, then the sibling routing — a sensible order. It is slightly long and the parenthetical '(additive and not idempotent)' plus 'A canonical POST' phrasing is redundant with the annotations, but no sentence is pure filler.

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?

No output schema exists, yet the description fully specifies the return shape (ID, timestamp, content hash, stable URLs) and the immutability contract. Combined with the routing to get_report_snapshot for reads, an agent has everything needed to invoke and consume the result correctly.

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 already document their constraints (domain format restriction, format enum), so the description cannot add much. It only gestures at the two renderings by mentioning 'JSON and Markdown renderings,' which roughly mirrors the format enum rather than extending it. Baseline 3 is appropriate.

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?

Specific verb ('Create') plus specific resource ('immutable evidence snapshot of the current Everything Report for a domain'), and it enumerates what is returned. It explicitly distinguishes itself from both siblings it could be confused with: get_everything_report (live read) and get_report_snapshot (read-back).

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?

Gives an explicit selection rule: 'Use this instead of get_everything_report when the result must remain stable,' and names the follow-up read path via get_report_snapshot. It also names concrete use cases (tickets, audit trails, NIS2/ISO evidence, LLM citations) so the agent knows the triggering context.

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.