Skip to main content
Glama

Domain Security Report - DMARC, SPF, SSL, headers, WHOIS in one call

domain_security_report
Read-onlyIdempotent

One call, one domain, every check: DMARC/SPF/DKIM/MX score with the exact DNS records to fix, security headers grade and SSL certificate days left, WHOIS/RDAP age, expiry and registrar, plus a merged top-issues list. ~1-2 s. Free: 25 calls/day per IP. Paid: $0.01 per call via x402 at https://radarbg.com/x402/domain-security-report.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "github.com"
    },
    "name": "domain_security_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: ~1-2 s latency, a 25 calls/day per-IP free quota, and a $0.01 per-call paid path via x402, which an agent needs to decide whether to call. It stops short of describing failure modes or what happens for unregistered domains.

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?

Front-loaded with the core capability, then scope, then latency/pricing in short sentences. Every clause carries information an agent would otherwise have to guess at; there is no filler.

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 no output schema, the description must convey return contents, and it does so thoroughly via the enumeration of checks and the merged top-issues list. Missing only edge-case behavior (invalid or unregistered domains, partial-failure results) for a fully complete picture.

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 100% for the single 'domain' parameter, so the baseline is 3. The description adds only the mild implication that exactly one domain is handled per call (no batching), without any syntax, normalization or TLD guidance beyond the schema's own example.

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

Purpose5/5

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

States a specific verb and resource (report on one domain in one call) and enumerates exactly what it returns: DMARC/SPF/DKIM/MX scores, security headers grade, SSL days left, WHOIS/RDAP age, expiry, registrar, and a merged issue list. That enumeration is specific enough that an agent can infer it is the broad 'everything at once' check rather than a narrow scan.

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 by the scope ('one call, one domain, every check'), and the description supplies operational guidance on cost and latency. However, it never states when to pick this over look-alike siblings such as domain_intel or security_scan, nor any prerequisites or exclusions, so the agent must infer the choice.

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