Skip to main content
Glama

BRAINIAC Domain Security

Audit domain infrastructure consistency

domain-security_domain-infrastructure-consistency-audit

Compare caller-supplied DNS answers, certificate names, addresses, prefixes, and RPKI results for one domain. audit_status is consistent, inconsistencies_detected, warnings, or incomplete. risk_level is low, medium, high, or critical. No DNS, TLS, WHOIS, or BGP lookup is performed. Price $0.05 USDC. POST /api/v1/domain-security/domain-infrastructure-consistency-audit. Unpaid calls return 402 and do 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": {
      "domain": "<domain>",
      "snapshot": "<snapshot>"
    },
    "name": "domain-security_domain-infrastructure-consistency-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeNo
domainYes
expectedNo
previousNo
snapshotYes
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description does substantial work: it discloses that no external DNS/TLS/WHOIS/BGP lookups occur (so no live side effects), states the price and that unpaid calls return 402 without running, and enumerates the audit_status and risk_level values. It stops short of stating auth/payment mechanics or whether results include per-item detail.

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?

Front-loaded with the core purpose and followed by terse, high-value facts (output enums, no lookups, price, endpoint, 402 behavior). Slightly list-like and the endpoint/price sentences sit between semantic content, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 6-parameter tool with nested objects and no output schema, the description covers cost, side effects, and two key response fields, which is meaningful. However, the input model (which fields go where and why) and the remainder of the response shape remain unaddressed, leaving gaps an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters with deep nesting, so the description must compensate. It broadly names the data categories compared (DNS answers, certificates, addresses, prefixes, RPKI), but never explains the distinct roles of `snapshot` vs `previous` vs `expected` vs `edge`, nor `checkedAt` — leaving the most consequential parameter semantics undocumented.

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 ('Compare') and a concrete resource set (caller-supplied DNS answers, certificate names, addresses, prefixes, RPKI results) for one domain. The clause 'No DNS, TLS, WHOIS, or BGP lookup is performed' implicitly distinguishes this from the sibling *-audit tools that do live lookups, though no sibling is named directly.

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 context is only implied: the agent can infer this is for comparing user-collected snapshots rather than running live discovery. There is no explicit 'use this instead of X when Y' guidance and no stated prerequisites such as 'snapshot must be pre-collected'.

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