Skip to main content
Glama

domfacts__dns

DNS records for a domain: A, AAAA, MX, TXT, NS, CNAME, SOA, CAA. 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/domfacts/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": "domfacts__dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"Domain name, e.g. example.com"
    • addedInput schema / required
      Added value: +[
      +  "domain"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the critical behavioral fact that each call costs $0.01 USDC on Base and requires an x402 payment object in params._meta, which is exactly the kind of context an agent needs before invoking. It omits error behavior (no records found, invalid domain), rate limits, and whether lookups are cached or live.

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?

Three tight clauses, front-loaded with the resource and record types, then pricing and transport. The raw HTTP URL is somewhat redundant for most agents but is at least compact and factual.

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?

For a one-parameter read with no output schema, the record-type enumeration effectively previews the return shape and the payment terms are spelled out. However, with no annotations to fall back on, the description should also cover failure modes and whether a payment envelope is strictly mandatory.

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% with a single documented parameter (domain, with an example), so the schema already does the work. The description adds no domain-syntax detail beyond the record-type list, which describes output rather than input.

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?

"DNS records for a domain" names the resource and the exact record types returned (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA), so an agent knows precisely what it gets. It does not differentiate from siblings like domain_intel__dns or domfacts__rdap, and the verb is implied rather than stated.

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?

No guidance on when to choose this over domain_intel__dns, domfacts__rdap, or domain_intel__lookup, all of which overlap. There is no mention of prerequisites beyond payment, and no when-not-to-use conditions.

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