Skip to main content
Glama

BlackVeil DNS & Email Security Scanner

by com.blackveilsecurity
OverviewDiscussionsAdmin

delete_brand_audit_watch

DestructiveIdempotent

Permanently removes a recurring brand-audit watch by watchId. Owner-scoped — a watchId owned by another principal surfaces as notFound. Returns confirmation of deletion.

Input Schema

NameRequiredDescriptionDefault
formatNoOutput verbosity. Auto-detected if omitted.
watchIdYesWatch ID returned by register_brand_audit_watch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Output verbosity. Auto-detected if omitted.",
+  "enum": [
+    "full",
+    "compact"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • 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
  3. Changed1 schema field changed
    • addedOutput schema / properties / verdictWithheld
      Added value: +{
+  "type": "boolean"
+}
  4. Changed2 schema fields changed
    • addedOutput schema / properties / checkStatus
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / partial
      Added value: +{
+  "type": "boolean"
+}
  5. 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"
+}
  6. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, so the description need not repeat safety hints. It adds meaningful context beyond annotations: permanent removal, owner-scoped access, and notFound behavior for another principal's watchId. It also states that deletion confirmation is returned.

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 short sentences, front-loaded with the action and key constraint. No filler; the ownership and return-value details each add useful information.

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?

For a simple destructive delete with annotations covering safety and idempotency, the description covers the key behavioral traits: permanence, ownership scoping, and confirmation of deletion. It could clarify what the confirmation contains, but no output schema exists and the gap is minor.

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 schema already documents watchId as the ID returned by register_brand_audit_watch and format as output verbosity. The description only restates that deletion is by watchId, so it meets the baseline without adding syntax or format detail 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?

The description names a specific verb and resource: 'Permanently removes a recurring brand-audit watch by watchId.' It is immediately distinguishable from sibling tools like register_brand_audit_watch and list_brand_audit_watches.

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?

Usage is implied by the delete semantics and required watchId, but the description does not explicitly say when to use this versus listing watches first or what prerequisites exist. It provides enough context to infer the operation but no explicit when/when-not guidance.

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