Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Audit a BIND zone file

network-exposure_dns-zone-audit
Read-onlyIdempotent

Flag dangling CNAMEs, wildcards, missing CAA/SPF/DMARC and TTL anomalies. Price $0.03 USDC. POST /api/v1/network-exposure/dns-zone-audit. An unpaid call returns the x402 payment terms and does not run.

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": {
      "zone": "<zone>"
    },
    "name": "network-exposure_dns-zone-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneYeszone, string, length 1 to 5000000. Required.
maxTtlNomaxTtl, integer, from -9007199254740991 to 9007199254740991. Required.
minTtlNominTtl, integer, from -9007199254740991 to 9007199254740991. Required.
originNoorigin, string, length 0 to 255. Optional.
deprovisionedTargetsNodeprovisionedTargets, array. Required.

Output Schema

NameRequiredDescriptionDefault
spfNospf. Object.
originNoorigin. String.
recordsNorecords. Number.
sourcesNosources. Array.
findingsNofindings. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds genuinely new behavior: a $0.03 USDC price and the critical detail that an unpaid call returns x402 payment terms and does not execute. It does not describe result shape or size limits on the zone input, but the output schema carries that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, findings front-loaded ahead of pricing and endpoint. Nothing is redundant, though the telegraphic noun-list style leaves the first sentence without a subject verb and the endpoint string is of limited use to an agent.

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?

With annotations, a full input schema, and an output schema present, the description covers the remaining gaps that structured fields cannot: what is detected and how billing gates execution. The one omission is that the zone parameter's meaning (raw file contents up to 5MB) must be inferred from the title.

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 already documents all five parameters, and this is the baseline case. The description adds only indirect hints (TTL anomalies maps to minTtl/maxTtl, dangling CNAMEs maps to deprovisionedTargets) and never clarifies that the zone parameter is the file content itself.

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?

The description gives a specific verb ("Flag") and enumerates concrete findings: dangling CNAMEs, wildcards, missing CAA/SPF/DMARC, TTL anomalies. Combined with the title "Audit a BIND zone file", an agent knows exactly what resource is inspected and what it returns, though it never explicitly distinguishes itself from the sibling dnssec-validate-offline.

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 only implied: you bring a zone and get misconfiguration findings. There is no statement of prerequisites, when to prefer this over network-exposure_dnssec-validate-offline, or whether the zone must be a raw BIND file versus a domain name. The payment gating is a constraint, not usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources