BlackVeil DNS & Email Security Scanner

compare_baseline

Read-onlyIdempotent

Compare a domain's current security configuration against a fixed policy baseline to determine compliance. Use to check whether a domain meets a policy requirement — not for tracking improvement/regression over time (use analyze_drift) and not for comparing multiple domains (use compare_domains).

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": {
      "domain": "<domain>",
      "baseline": "<baseline>"
    },
    "name": "compare_baseline"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	Domain to scan and compare.
`format`	No	Output verbosity.
`baseline`	Yes	Required-controls policy (grade/score floors, require_* flags). Not a prior scan; see analyze_drift.
`force_refresh`	No	Bypass the cache.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 12, 2026

changedInput schema / properties / baseline / description

Previous value: -"Policy/requirements baseline OBJECT for compliance enforcement — \"does this domain meet these required controls?\" (grade/score floors, require_* flags, max_*_findings). NOT a prior scan. For drift-over-time vs a previous ScanScore (or the literal \"cached\"), use analyze_drift instead."New value: +"Required-controls policy (grade/score floors, require_* flags). Not a prior scan; see analyze_drift."

changedInput schema / properties / force_refresh / description

Previous value: -"Bypass cache and run a fresh check. Useful after DNS changes."New value: +"Bypass the cache."

changedInput schema / properties / format / description

Previous value: -"Output verbosity. Auto-detected if omitted."New value: +"Output verbosity."

Changed2 schema fields changedOct 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- changedInput schema / properties / baseline / additionalProperties
```
Previous value: -{}New value: +false
```

Changed2 schema fields changedJul 2, 2026

changedInput schema / properties / baseline / description

Previous value: -"Policy baseline requirements."New value: +"Policy/requirements baseline OBJECT for compliance enforcement — \"does this domain meet these required controls?\" (grade/score floors, require_* flags, max_*_findings). NOT a prior scan. For drift-over-time vs a previous ScanScore (or the literal \"cached\"), use analyze_drift instead."

addedInput schema / properties / force_refresh

Added value: +{
+  "description": "Bypass cache and run a fresh check. Useful after DNS changes.",
+  "type": "boolean"
+}

First observedApr 21, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds that the baseline is a fixed policy target rather than a prior scan, but says nothing about caching or how force_refresh affects results, and nothing about what compliance output looks like.

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 sentences, zero waste, with the purpose front-loaded and the exclusions immediately after. Each clause carries a distinct routing signal.

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?

Given a fully documented four-parameter schema and annotations covering the safety profile, the description supplies the routing decision an agent actually needs. The only shortfall is the absence of any hint about result shape or how findings map to a pass/fail verdict, which matters since no output schema exists.

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% and the nested baseline object documents every flag, so the baseline of 3 applies. The description reinforces that baseline is a required-controls policy, not a prior scan — useful disambiguation but no additional format or semantics beyond the schema.

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: compare a domain's current security configuration against a fixed policy baseline to determine compliance. The negative framing (compare vs. track over time vs. compare domains) makes the boundary with siblings unambiguous.

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 says when to use (check whether a domain meets a policy requirement) and when not to (not for improvement/regression tracking — use analyze_drift; not for multiple domains — use compare_domains). Both alternative routes are named with their selecting conditions.

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 tools Inspect

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.