Skip to main content
Glama
MadaBurns

Blackveil DNS

by MadaBurns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_brand_audit_watches

Read-onlyIdempotent

List your recurring brand-audit watches to review domains, check intervals, webhook presence, last-run times, and active status. Read-only and scoped to your owner account.

Instructions

Returns the caller's recurring brand-audit watches: watchId, domain, interval, webhook presence, last-run time, and active state. Owner-scoped. Read-only.

Input Schema

NameRequiredDescriptionDefault
formatNoOutput verbosity. Auto-detected if omitted.

Output Schema

NameRequiredDescriptionDefault
scoreYes
passedYes
partialNo
categoryYes
findingsYes
checkStatusNo
verdictWithheldNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.103.1
    • 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 changedv3.98.1
    • addedOutput schema / properties / verdictWithheld
      Added value: +{
+  "type": "boolean"
+}
  3. Changed2 schema fields changedv3.54.0
    • addedOutput schema / properties / checkStatus
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / partial
      Added value: +{
+  "type": "boolean"
+}
  4. Addedv3.37.0
  5. Removedv3.31.1
  6. First observedv3.29.7

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaningful context those annotations cannot: results are owner-scoped (the caller only) and only webhook presence is exposed, which implies no secret leakage.

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, front-loaded fragments: what is returned, the ownership scope, and the safety profile. No redundancy and the most decision-relevant information comes first.

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?

A simple owner-scoped list operation with full annotation coverage, a complete output schema, and a fully described single optional parameter. Nothing an agent needs to select or invoke it correctly is missing.

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?

One optional `format` enum with 100% schema description coverage, so the schema already documents verbosity and its auto-detection default. The description adds nothing about output shape differences between full and compact, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (returns the caller's recurring brand-audit watches) and enumerates the returned fields, which clearly separates it from register_brand_audit_watch and delete_brand_audit_watch. It stops short of explicitly naming those siblings, so differentiation is inferred rather than stated.

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?

Describes the read context ('Owner-scoped. Read-only.') but never says when to call this versus register/delete or the brand_audit_status tools. Usage is implied by the list semantics rather than spelled out.

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