Skip to main content
Glama
Sign In

BlackVeil DNS & Email Security Scanner

by com.blackveilsecurity
OverviewDiscussionsAdmin

batch_scan_start

Idempotent

Start a durable asynchronous scan of 1–10 domains. Returns a stable job ID; replaying the same idempotency key with the same principal, normalized inputs, and scoring versions returns the same job.

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": {
      "domains": "<domains>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "batch_scan_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput verbosity.
domainsYesDomains to scan (max 10 per request)
force_refreshNoBypass the cache.
idempotency_keyYesCaller-stable replay key for this exact batch request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / force_refresh / description
      Previous value: -"Bypass cache and run fresh scans."New value: +"Bypass the cache."
    • changedInput schema / properties / format / description
      Previous value: -"Output verbosity. Auto-detected if omitted."New value: +"Output verbosity."
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, so the credit here comes from explaining replay semantics: same idempotency key plus same principal, normalized inputs, and scoring versions yields the same job. That adds real behavioral context the annotations only assert. It stops short of describing durability windows, cost, or failure/partial-result behavior.

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?

Two tight sentences, front-loaded with what the tool does and the hard 1–10 limit, then the return value and idempotency contract. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the essentials for a durable start tool: scope limit, returned job ID, and replay guarantees. A brief pointer to the status/findings tools would close the only meaningful gap, since no output schema exists to describe the job handle.

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 description coverage is 100%, so the schema already documents all four parameters, including the enum for format and the idempotency key's role. The description reinforces the domain-count bound and the replay contract but adds no format, syntax, or normalization details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Start a durable asynchronous scan of 1–10 domains") and names the returned handle (stable job ID). It is distinguishable from status/findings siblings by the "start" framing, though it never explicitly routes to batch_scan_status or contrasts with batch_scan.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this is the entry point for a batch scan and that a follow-up status/findings call is expected, but it never states when to use this versus batch_scan, scan_domain, or brand_audit_batch_start. No exclusions or prerequisites are given beyond the domain count limit.

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

All BlackVeil 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