Skip to main content
Glama
MadaBurns

Blackveil DNS

by MadaBurns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

brand_audit_batch_start

Start an asynchronous brand audit for up to 50 domains, returning an audit ID for polling status and retrieving results.

Instructions

Enqueue an async brand audit across up to 50 target domains with optional standard/deep discovery depth, brand aliases, and caller-supplied candidate domains. Returns { auditId, queuedAt, targetCount, etaSeconds } immediately; poll with brand_audit_status and fetch results with brand_audit_get_report once complete. Each target consumes 1 unit of the monthly BRAND_AUDIT_QUOTAS budget.

Input Schema

NameRequiredDescriptionDefault
viewNoOutput view mode. 'registrar_complement' produces a registrar-complement payload; requires enterprise tier. Default 'standard'.
depthNoDiscovery depth. standard is default; deep expands candidate seeding and enrichment fanout.
formatNoInline output mode. Defaults to "both".
domainsYesDomains to audit (max 50 per batch). Duplicates are merged.
planner_modeNoPlanner mode for staged discovery fanout. observe emits metrics; enforce applies candidate-backed signal caps.
brand_aliasesNoOptional public brand aliases to seed, such as product or legal-entity labels.
discovery_modeNoBrand-discovery pipeline mode. classic = legacy sweep; tiered = tenant/graph/evidence wrappers first (BlackVeil-internal).
min_confidenceNoDrop candidates whose combined confidence falls below this threshold (0-1, default 0.5).
candidate_domainsNoOptional candidate domains supplied by the caller for corroboration.
ownership_verifiedNoCaller attests that the target domains are owned or authorized for scanning. Required when discovery_mode is "tiered" and the caller is not an enterprise/owner/partner principal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.103.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": {},
-  "properties": {
-    "category": {
-      "type": "string"
-    },
-    "checkStatus": {
-      "type": "string"
-    },
-    "findings": {
-      "items": {
-        "additionalProperties": {},
-        "properties": {},
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "partial": {
-      "type": "boolean"
-    },
-    "passed": {
-      "type": "boolean"
-    },
-    "score": {
-      "type": "number"
-    },
-    "verdictWithheld": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "category",
-    "score",
-    "passed",
-    "findings"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changedv3.98.1
    • addedOutput schema / properties / verdictWithheld
      Added value: +{
+  "type": "boolean"
+}
  3. Changed2 schema fields changedv3.78.0
    • changedInput schema / properties / view / description
      Previous value: -"Output view mode. 'csc_complement' produces a CSC-tuned payload; requires enterprise tier. Default 'standard'."New value: +"Output view mode. 'registrar_complement' produces a registrar-complement payload; requires enterprise tier. Default 'standard'."
    • changedInput schema / properties / view / enum
      Previous value: -[
-  "standard",
-  "csc_complement"
-]New value: +[
+  "standard",
+  "registrar_complement"
+]
  4. Changed2 schema fields changedv3.54.0
    • addedOutput schema / properties / checkStatus
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / partial
      Added value: +{
+  "type": "boolean"
+}
  5. First observedv3.29.7

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond annotations by disclosing the quota cost (1 unit per target against monthly BRAND_AUDIT_QUOTAS), async behavior, and the immediate return shape. These are non-obvious operational traits that materially affect invocation decisions.

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 tightly packed sentences, front-loaded with the core action, then return/poll guidance, then quota cost. Zero waste.

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?

Strong coverage for a complex 10-param tool: workflow, return shape, and quota are all addressed. However, advanced params like planner_mode, discovery_mode, view, and ownership_verified are left entirely to the schema with no prose context.

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 all 10 parameters are already documented. The description restates a few (domains, depth, aliases, candidate domains) but adds no format or behavioral detail beyond the schema. Baseline 3 is appropriate.

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+resource ('Enqueue an async brand audit') with scope (up to 50 target domains), clearly distinguishing it from the single-domain sibling brand_audit_single.

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?

Explicitly describes the async workflow: poll with brand_audit_status and fetch results with brand_audit_get_report once complete. Lacks explicit contrast against brand_audit_single or batch_scan_start, but the follow-up routing is clear.

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

Deploy Server

Other Tools