Skip to main content
Glama

domain_intel__dns

Domain intelligence: full DNS/SPF/DMARC report, WHOIS age, TLS, and an AI-crawler policy check (robots.txt verdict per AI bot, llms.txt, sitemap). GET with a domain param. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/domain-intel/dns

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_intel__dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain or URL, e.g. example.com or https://example.com/page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"Domain or URL, e.g. example.com or https://example.com/page"
    • addedInput schema / required
      Added value: +[
      +  "domain"
      +]
  2. Changed2 schema fields changed
    • removedInput schema / properties / domain / description
      Removed value: -"Domain name to inspect, e.g. github.com"
    • removedInput schema / required
      Removed value: -[
      -  "domain"
      -]
  3. Changed2 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"Domain name to inspect, e.g. github.com"
    • addedInput schema / required
      Added value: +[
      +  "domain"
      +]
  4. Changed2 schema fields changed
    • removedInput schema / properties / domain / description
      Removed value: -"Domain name, e.g. example.com"
    • removedInput schema / required
      Removed value: -[
      -  "domain"
      -]
  5. Changed2 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"Domain name, e.g. example.com"
    • addedInput schema / required
      Added value: +[
      +  "domain"
      +]
  6. Changed2 schema fields changed
    • removedInput schema / properties / domain / description
      Removed value: -"Domain to check, e.g. github.com"
    • removedInput schema / required
      Removed value: -[
      -  "domain"
      -]
  7. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain to check"New value: +"Domain to check, e.g. github.com"
  8. Changed2 schema fields changed
    • removedInput schema / properties / domains
      Removed value: -{
      -  "description": "Comma-separated domains: up to 10 for /batch, up to 25 for /portfolio",
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "domain"
      +]
  9. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Single domain for /dns, /lookup, /email"New value: +"Domain to check"
  10. Changed3 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Single domain for /dns, e.g. example.com"New value: +"Single domain for /dns, /lookup, /email"
    • changedInput schema / properties / domains / description
      Previous value: -"Comma separated domains: up to 10 for /batch, up to 25 for /portfolio"New value: +"Comma-separated domains: up to 10 for /batch, up to 25 for /portfolio"
    • removedInput schema / required
      Removed value: -[
      -  "domains"
      -]
  11. Changed3 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Public domain name, e.g. example.com"New value: +"Single domain for /dns, e.g. example.com"
    • changedInput schema / properties / domains / description
      Previous value: -"For /batch: comma separated domains, max 10"New value: +"Comma separated domains: up to 10 for /batch, up to 25 for /portfolio"
    • addedInput schema / required
      Added value: +[
      +  "domains"
      +]
  12. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does disclose genuinely important behavior: a $0.01 per-call charge in USDC on Base (eip155:8453) settled via x402 at params._meta["x402/payment"], plus the HTTP verb and endpoint. It does not state what happens on payment failure, whether the call is cached or rate limited, or how large a response is returned — notable gaps for a paid tool.

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 highest-value information — what the report contains — is front-loaded, followed by payment terms and the endpoint. Redundancy is minor: 'GET with a domain param' and the trailing 'HTTP: GET ...' restate the same method, costing a few words.

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?

With no output schema, the description does the right thing by enumerating the report's sections, and it covers the payment prerequisite, so an agent can call it successfully. However, for a paid composite-intelligence endpoint it says nothing about response shape, size, partial-failure behavior, or latency, leaving an agent unable to anticipate what it will receive for its penny.

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?

Coverage is 100% for the single parameter, and the schema already explains that a bare domain or a full URL is acceptable. The description's 'GET with a domain param' adds no meaning beyond that. With one well-documented parameter, the baseline of 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?

The description enumerates exactly what the tool returns: DNS/SPF/DMARC records, WHOIS age, TLS, and an AI-crawler policy check with robots.txt verdicts, llms.txt, and sitemap. That is specific enough to distinguish it from a pure DNS lookup, but it never names the overlapping siblings (domain_intel__policy, domain_intel__lookup, domainkit__dns), so the agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives, despite several sibling tools covering adjacent surfaces such as policy and lookup. The only usage instruction is mechanical — 'GET with a domain param' — which is a calling convention rather than selection guidance.

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