Skip to main content
Glama
Sign In

IntoDNS.ai DNS & Email Security Scanner

by ai.intodns
OverviewDiscussionsAdmin

Cancel deep scan

cancel_deep_scan
Idempotent

Cancel an in-progress Internet.nl deep scan. Marks the scan cancelled; the polling loop then withdraws the upstream Internet.nl batch, usually within ten seconds. Requires scanId returned by start_deep_scan. Nothing is deleted: a scan that already finished keeps its results and is left alone, so calling this twice is safe. An unknown or expired scanId returns 404. Use when the user changes their mind mid-scan or when polling get_deep_scan_status would otherwise time out. No auth.

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

Input Schema

NameRequiredDescriptionDefault
scanIdYesDeep scan ID returned by start_deep_scan

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: describes the mechanism (marks cancelled, polling loop withdraws the upstream batch in ~10s), the non-destructiveness in concrete terms (nothing deleted, finished results preserved), idempotency rationale ('calling this twice is safe'), error behavior (404 for unknown/expired scanId), and 'No auth'. All consistent with readOnlyHint=false, idempotentHint=true, destructiveHint=false.

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 purpose and effect, then mechanics, then safety, then error behavior, then usage triggers. Dense and efficient, though the usage guidance lands last when it could be nearer the top, and the semicolon-chained first two sentences are slightly heavy.

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 covers what happens on success, on repeat calls, on already-finished scans, and on unknown IDs. For a single-parameter cancel tool with annotations already covering safety flags, nothing an agent needs is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the scanId description already points at start_deep_scan, so baseline is 3. The description adds meaningful value by explaining the failure mode for a bad ID (404) and that the ID must come from a live scan, not an arbitrary string.

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 ('Cancel an in-progress Internet.nl deep scan') and immediately distinguishes its scope from the sibling pair start_deep_scan / get_deep_scan_status. An agent knows exactly which phase of the scan lifecycle this tool occupies.

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 when-to-use conditions ('user changes their mind mid-scan' or 'polling get_deep_scan_status would otherwise time out') and an implicit when-not via 'a scan that already finished keeps its results and is left alone'. Names the sibling it complements and the parameter source from start_deep_scan.

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