Skip to main content
Glama

Domain due-diligence and risk report

domain_report
Read-only

Due-diligence report on a website, merchant or counterparty domain: registrable domain, registry RDAP facts (registrar, abuse contact, created, expiry, age, status, nameservers), DNS records (A, AAAA, MX, NS, TXT, CAA) from Cloudflare DNS over HTTPS, SPF and DMARC posture, a live web probe (redirect chain, HTTPS, HSTS, site-supplied title, parked or for-sale signs), brand-impersonation checks, and a 0-100 risk score with transparent weighted signals and a verdict. Price: $0.01 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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>"
    },
    "name": "domain_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesBare domain, hostname, email address or URL. Scheme, path, port and credentials are stripped and IDNs are converted to punycode. IP addresses and private names are rejected.

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 only declare readOnlyHint and openWorldHint, so the added context matters: the description discloses data provenance (registry RDAP, Cloudflare DoH, live probe), the fact that scoring is transparent and weighted, and a precise billing model ($0.01 per successful call via x402 v2, failures and empty matches uncharged). It still says nothing about latency, caching or response format.

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?

Purpose is front-loaded and the long enumeration is dense with decision-relevant detail rather than filler. The second sentence on pricing is separate and clearly scoped, though the first sentence is a run-on list that could be broken up.

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 effectively doubles as a return-value summary by listing every section the report contains, which is exactly what an agent needs to judge relevance. Minor gaps remain around response format and any rate or size limits for a tool that performs multiple live network probes.

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% and the single parameter already documents normalization (scheme/path/port stripping, IDN punycode) and rejection of IPs and private names. The description adds no additional input semantics, so baseline 3 applies.

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?

Names a specific deliverable (due-diligence risk report) plus the resource (domain) and then enumerates the exact contents: RDAP facts, DNS records, SPF/DMARC, live probe, impersonation checks, 0-100 risk score. That enumeration implicitly separates it from the narrower siblings domain_dns, domain_whois and domain_email_auth, though it never names them explicitly as the single-aspect alternatives.

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 by the phrase 'due-diligence report on a website, merchant or counterparty domain'; there is no explicit statement of when to call this versus the narrower domain_* tools, and no exclusions or prerequisites beyond the schema's rejection rules.

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