Skip to main content
Glama
Sign In

BlackVeil DNS & Email Security Scanner

by com.blackveilsecurity
OverviewDiscussionsAdmin

batch_scan

Read-onlyIdempotent

Bulk-scan up to 10 domains in parallel with a full security audit each; returns score, NIST-aligned letter grade (A+ to F) and finding counts per domain. Use to audit several domains at once; use compare_domains for a side-by-side comparison of 2-5 domains. scoringModelVersion (policy) is independent of dnsChecksPackageVersion (engine); cite scoringConfigHash with scores.

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>"
    },
    "name": "batch_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput verbosity.
domainsYesDomains to scan (max 10 per request)
force_refreshNoBypass the cache.

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. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: parallel execution, a hard 10-domain cap, and the fact that scoringModelVersion (policy) is independent of dnsChecksPackageVersion (engine) with scoringConfigHash required for citation. It does not disclose runtime expectations or partial-failure behavior for invalid domains.

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?

The purpose and the batch limit are front-loaded, and the routing sentence to compare_domains follows immediately. The closing versioning sentence is dense and somewhat orthogonal to tool selection, but it earns its place by preventing a misattributed score citation.

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?

With no output schema, the description does the necessary work of summarizing the return shape (per-domain score, letter grade, finding counts) and the versioning metadata needed to report results correctly. The remaining gap is operational: nothing about what happens to the other nine domains if one fails, or about latency/async behavior.

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 all three parameters (format, domains, force_refresh) are already documented at the field level, and the description adds no new syntax or format guidance for them. The versioning sentence describes return-side metadata rather than input semantics, 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?

The description states a specific verb and resource ("Bulkscan up to 10 domains") plus the scope of work ("full security audit each") and even summarizes the return payload (score, NIST-aligned letter grade, finding counts). It explicitly contrasts itself with compare_domains, so an agent can separate the two without opening either schema.

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

Usage Guidelines4/5

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

It gives a clear use condition ("audit several domains at once") and names a specific alternative with the selection rule (compare_domains for 2-5 domain side-by-side comparison). It stops short of addressing the async siblings batch_scan_start/status/findings, so an agent has no stated cue for when this synchronous-looking call is preferable to starting a job.

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