Skip to main content
Glama

Get report snapshot

get_report_snapshot
Read-onlyIdempotent

Read a previously created IntoDNS.ai Everything Report evidence snapshot by snapshot ID. Read-only GET — returns the immutable JSON report exactly as it was at snapshot creation, with the original SHA-256 content hash and timestamp.

Instructions

Read a previously created IntoDNS.ai Everything Report evidence snapshot by snapshot ID. Read-only GET — returns the immutable JSON report exactly as it was at snapshot creation, with the original SHA-256 content hash and timestamp. Requires snapshotId from create_report_snapshot. Use to verify or re-read an audit-trail evidence record without re-running a live scan; use get_everything_report for current live data instead. No auth, fully idempotent.

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": {
      "snapshotId": "<snapshotId>"
    },
    "name": "get_report_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoReturn JSON data or LLM-ready Markdownjson
snapshotIdYesSnapshot ID returned by create_report_snapshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

It discloses traits beyond the annotations: the report is immutable, carries its original SHA-256 content hash and timestamp, and needs no auth. It repeats the idempotency annotation, but the immutability and evidence-integrity details meaningfully extend the read-only/idempotent contract.

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?

Three dense sentences that front-load the action and resource, then usage guidance. Every sentence earns its place, with no filler or repetition.

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 two-parameter read tool with full annotations and complete schema coverage, the description covers purpose, prerequisite, return shape, and alternatives. The only omission is the format option, which the schema already handles.

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%, with both parameters documented, including the snapshotId source and the format enum. The description reinforces where snapshotId comes from but never mentions the markdown format option, so it does not go beyond what the schema already provides.

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 (read) and resource (a previously created IntoDNS.ai Everything Report evidence snapshot), keyed by snapshot ID, and specifies what it returns: the immutable JSON report as it was at creation. It is clearly distinguishable from create_report_snapshot and get_everything_report.

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?

Explicitly says when to use it (verify or re-read an audit-trail evidence record without re-running a live scan) and names the alternative for the opposite case (get_everything_report for current live data). It also states the prerequisite that snapshotId comes from create_report_snapshot.

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