Skip to main content
Glama

BRAINIAC Domain Security

Grade domain snapshot health

domain-security_infrastructure-health

Look through the supplied DNS records, certificate names, expiry date, and cipher names. A CNAME whose target has no A or AAAA in the snapshot, a certificate that omits the domain, an expiry before the supplied date, a weak cipher name, or a missing NS record raises the exposure. The grade follows that percentage. No DNS or TLS lookup is performed. Price $0.04 USDC. POST /api/v1/domain-security/infrastructure-health. 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>",
      "as_of": "<as_of>",
      "records": "<records>",
      "certificate": "<certificate>"
    },
    "name": "domain-security_infrastructure-health"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofYes
domainYes
recordsYes
certificateYes

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 carries the full behavioral burden and discloses important traits: it is a snapshot-only evaluation, it costs $0.04 USDC, unpaid calls return 402 without running, and several exposure-raising conditions are described. It does not describe the output shape or grading thresholds in 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?

The description is reasonably front-loaded with the core evaluation logic and avoids excessive repetition. It includes operational details such as price, endpoint, and 402 behavior, which are useful but make it slightly procedural rather than purely definitional.

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?

The tool has four required parameters including nested objects, no annotations, no output schema, and 0% schema description coverage. The description supplies important behavioral context and some input concepts, but it leaves substantial gaps around parameter details and the meaning or format of the returned grade.

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%, so the description must compensate for the silent schema. It names the input concepts (DNS records, certificate names, expiry date, cipher names) but does not map them to required parameters, explain the nested records/certificate structure, or clarify constraints such as as_of and domain.

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 states a specific action: grade a supplied domain snapshot using DNS records and certificate details, without performing lookups. It is clear what the tool does, but it does not explicitly differentiate itself from the sibling audit tools by name.

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: supply a snapshot to receive a grade, and do not expect the tool to perform DNS or TLS lookups. There is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives among the sibling tools.

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