Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Validate DNSSEC records offline

network-exposure_dnssec-validate-offline
Read-onlyIdempotent

Check DNSKEY, DS and RRSIG material without network queries. Price $0.04 USDC. POST /api/v1/network-exposure/dnssec-validate-offline. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "network-exposure_dnssec-validate-offline"
  }
}

Input Schema

NameRequiredDescriptionDefault
dsNods, array. Required.
nowNonow, string. Optional.
rrsetNorrset, array. Required.
rrsigsNorrsigs, array. Required.
dnskeysNodnskeys, array. Required.

Output Schema

NameRequiredDescriptionDefault
keysNokeys. Array.
secureNosecure. Boolean.
sourcesNosources. Array.
signaturesNosignatures. Array.
evaluatedAtNoevaluatedAt. String.
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?

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses pricing ($0.04 USDC), the endpoint, and crucially that an unpaid call returns x402 payment terms instead of executing. That payment-gate behavior is exactly the kind of operational fact annotations cannot express. The only weak spot is the mild tension with openWorldHint=true for a tool advertised as network-free.

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?

Three short sentences with the capability first, then cost, then the endpoint and payment fallback. No filler, though the raw POST path is arguably noise for an MCP caller and the price could be folded into a single clause.

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 an output schema present, the description needn't explain verdicts, and annotations cover the safety profile. It supplies the missing operational layer: offline execution and the x402 payment precondition. Only the string format expected for record material remains unstated.

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 nominally 100%, so the baseline of 3 applies, but the schema's own descriptions are tautological ("ds, array. Required."). The description names DNSKEY/DS/RRSIG, which maps loosely onto the dnskeys, ds, and rrsigs parameters, but adds no format, encoding, or rrset/now semantics beyond what the schema states.

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?

"Check DNSKEY, DS and RRSIG material" gives a specific verb plus the exact record types handled, and "without network queries" scopes the operation to offline validation. It is not tautological and clearly separable from a live DNS audit, though it never names a sibling to contrast with.

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?

The phrase "without network queries" implies the use case: validating records you already hold rather than fetching them. There is no explicit when-not-to-use guidance or pointer to a sibling such as the zone audit tool, so selection still depends on inference.

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