Skip to main content
Glama
Sign In

IntoDNS.ai DNS & Email Security Scanner

by ai.intodns
OverviewDiscussionsAdmin

Get deep scan status

get_deep_scan_status
Read-onlyIdempotent

Read-only status poll for a long-running Internet.nl deep scan. Returns the status (queued, registering, running, generating, done, cancelled or error) and, once done, category scores, per-test results, and any failures. Requires a scanId returned by start_deep_scan; poll every 10-30s until status is 'done', 'error' or 'cancelled'. Use after start_deep_scan; for fast single-vantage scans, prefer scan_domain. 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": {
      "scanId": "<scanId>"
    },
    "name": "get_deep_scan_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
scanIdYesDeep scan ID returned by start_deep_scan

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally. The description still adds valuable context beyond annotations: the full status lifecycle, polling cadence, no-auth, no side effects, and what becomes available once done (scores, per-test results, failures).

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?

Four compact sentences, front-loaded with the operation, then returns, then prerequisite/polling, then alternative. Every sentence carries useful information with no 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?

With no output schema, the description supplies return content (status values, scores, per-test results, failures). It also covers prerequisites, polling behavior, alternatives, and auth/side-effect expectations, leaving nothing essential for correct invocation.

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%, so the single scanId parameter is already documented in the schema as 'Deep scan ID returned by start_deep_scan'. The description reinforces the prerequisite relationship but adds no syntax or format detail beyond the schema, so baseline 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?

States a specific verb and resource ('read-only status poll for a long-running Internet.nl deep scan') and immediately distinguishes scope from siblings by naming start_deep_scan and scan_domain. An agent can identify the tool without opening the schema.

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 explicit trigger ('after start_deep_scan'), polling cadence ('every 10-30s'), termination conditions ('until done, error or cancelled'), and an alternative ('for fast single-vantage scans, prefer scan_domain'). This is close to ideal routing guidance.

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 toolsInspect
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.

Resources