Skip to main content
Glama

domain_intel__batch

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/batch

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Changed2 schema fields changed
    • addedInput schema / properties / domain
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / domains
      Removed value: -{
      -  "type": "string"
      -}
  6. Changed2 schema fields changed
    • removedInput schema / properties / domains / description
      Removed value: -"Comma-separated domain names"
    • removedInput schema / required
      Removed value: -[
      -  "domains"
      -]
  7. Changed3 schema fields changed
    • addedInput schema / properties / domains
      Added value: +{
      +  "description": "Comma-separated domain names",
      +  "type": "string"
      +}
    • removedInput schema / properties / url
      Removed value: -{
      -  "description": "Public https URL of the x402 endpoint to vet",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "url"
      -]New value: +[
      +  "domains"
      +]
  8. Changed3 schema fields changed
    • removedInput schema / properties / domains
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "Public https URL of the x402 endpoint to vet",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  9. Changed3 schema fields changed
    • removedInput schema / properties / domain
      Removed value: -{
      -  "description": "Domain to check, e.g. github.com",
      -  "type": "string"
      -}
    • addedInput schema / properties / domains
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "domain"
      -]
  10. Changed3 schema fields changed
    • addedInput schema / properties / domain
      Added value: +{
      +  "description": "Domain to check, e.g. github.com",
      +  "type": "string"
      +}
    • removedInput schema / properties / domains
      Removed value: -{
      -  "description": "Comma-separated domains, up to 10",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "domains"
      -]New value: +[
      +  "domain"
      +]
  11. Changed3 schema fields changed
    • removedInput schema / properties / domain
      Removed value: -{
      -  "description": "Domain to check",
      -  "type": "string"
      -}
    • 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"
    • addedInput schema / required
      Added value: +[
      +  "domains"
      +]
  12. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Single domain for /dns, /lookup, /email"New value: +"Domain to check"
  13. 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"
      -]
  14. 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"
      +]
  15. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose important operational facts: the call costs $0.01 USDC on Base (eip155:8453), payment goes in params._meta["x402/payment"], and the underlying request is an HTTP GET to a specific endpoint. However, it leaves out return shape, response size, latency, failure/refund behavior for paid calls, and any rate limits, so the behavioral picture is incomplete 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 capability list is front-loaded, then the invocation method, then price and payment mechanics, then the endpoint — a sensible order with little filler. It is dense but each clause (contents, payment, URL) carries distinct information an agent needs.

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?

There is no output schema, so the description appropriately enumerates what the report contains, and it covers the non-obvious payment handshake required to make the call succeed. It is nearly complete for a paid read-only report tool; only response format and failure semantics are unaddressed.

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?

There is a single required parameter with 100% schema description coverage, and the schema already documents that it accepts a bare domain or a full URL with example formats. The description only restates 'GET with a domain param', adding no accepted-format edge cases, normalization rules, or IDN/subdomain handling beyond what the schema provides.

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 names the resource (domain intelligence) and enumerates the concrete report contents: DNS/SPF/DMARC, WHOIS age, TLS, and AI-crawler policy including robots.txt verdicts per bot, llms.txt, and sitemap. It is clearly an aggregate report rather than a single-signal check, but it never explicitly contrasts itself with siblings like domain_intel__dns, domain_intel__lookup, or domain_intel__policy.

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: the word 'full' suggests this is the comprehensive option versus narrower siblings, and the presence of a price tag hints it is a paid step worth reserving for when a full report is needed. There is no explicit statement of when to prefer this over the cheaper single-purpose tools, nor any exclusions or prerequisites beyond the payment note.

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