Skip to main content
Glama

BlackVeil DNS & Email Security Scanner

by com.blackveilsecurity
OverviewDiscussionsAdmin

scan_buckets_start

Start an async cloud-bucket discovery scan for a target domain. Operator-deploy only; targets must be operator-authorized on the recon watchlist; degrades to info when unprovisioned. Returns a scanId immediately — poll progress with scan_buckets_status and retrieve results with scan_buckets_findings.

Input Schema

NameRequiredDescriptionDefault
targetYesDomain whose cloud buckets to discover (e.g. example.com).
providersNoCloud providers to scan (max 8, e.g. aws, gcp, azure). All providers if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / providers / description
      Added value: +"Cloud providers to scan (max 8, e.g. aws, gcp, azure). All providers if omitted."
    • addedInput schema / properties / target / description
      Added value: +"Domain whose cloud buckets to discover (e.g. example.com)."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": {},
-  "properties": {
-    "category": {
-      "type": "string"
-    },
-    "findings": {
-      "items": {
-        "additionalProperties": {},
-        "properties": {},
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "passed": {
-      "type": "boolean"
-    },
-    "score": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "category",
-    "score",
-    "passed",
-    "findings"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "category": {
+      "type": "string"
+    },
+    "findings": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "passed": {
+      "type": "boolean"
+    },
+    "score": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "category",
+    "score",
+    "passed",
+    "findings"
+  ],
+  "type": "object"
+}
  5. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already disclose non-readonly, non-idempotent, and open-world behavior. The description adds critical operational context: async execution, immediate scanId return, authorization prerequisites, and graceful degradation when unprovisioned.

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 tight sentences with no wasted words. The core purpose and constraints are front-loaded, and the follow-up guidance is concise.

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 is present, but the description explains the immediate return value (scanId) and explicitly names the follow-up tools for progress and results. It covers everything needed 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 description coverage is 100%, so the schema fully documents both parameters. The description does not add syntax or format details beyond what the schema provides, which is the expected baseline.

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 ('Start'), resource ('async cloud-bucket discovery scan'), and target scope. It clearly distinguishes the start phase from the sibling status and findings tools.

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 names the operational constraints: operator-deploy only, target must be operator-authorized, and degrades to info when unprovisioned. It also routes the agent to scan_buckets_status and scan_buckets_findings for the next steps.

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