AIPayGen Site Intel

DNS lookup

dns_lookup

Read-onlyIdempotent

Resolve DNS records for a domain (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA) and identify its DNS host and email provider. Price: $0.001 per call.

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": "dns_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`types`	No	Record types to fetch. Defaults to A, AAAA, MX, NS, TXT.
`domain`	Yes	Domain name, e.g. stripe.com

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 23, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / domain / description

Previous value: -"Domain to look up DNS records for"New value: +"Domain name, e.g. stripe.com"

removedInput schema / properties / domain / title
```
Removed value: -"Domain"
```

removedInput schema / properties / record_type

Removed value: -{
-  "default": "A",
-  "description": "DNS record type: A, AAAA, MX, TXT, NS, CNAME",
-  "title": "Record Type",
-  "type": "string"
-}

addedInput schema / properties / types

Added value: +{
+  "description": "Record types to fetch. Defaults to A, AAAA, MX, NS, TXT.",
+  "items": {
+    "enum": [
+      "A",
+      "AAAA",
+      "CNAME",
+      "MX",
+      "NS",
+      "TXT",
+      "SOA",
+      "CAA"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / title
```
Removed value: -"dns_lookupArguments"
```

AddedMar 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds a concrete cost signal ($0.001 per call), which is genuinely useful context, but says nothing about return shape, failure modes for unresolvable domains, or rate behavior. With annotations carrying the safety profile, a 3 is appropriate.

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?

A single front-loaded sentence with verb, resource, record types, derived outputs, and pricing — 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?

For a read-only, two-parameter lookup with full schema coverage and no output schema, the description covers purpose, scope, and cost. Slightly short on what the response contains (per-type records vs. summary) but otherwise sufficient.

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%, including the default set of record types, so the schema does the heavy lifting. The description restates the type list and domain purpose without adding syntax or validation detail beyond the schema.

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?

States a specific verb (Resolve) and resource (DNS records) and enumerates the supported record types, plus the extra derived outputs (DNS host, email provider). It does not explicitly contrast itself with siblings like domain_report, domain_whois, or email_security, so an agent must infer the boundary.

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?

The mention of identifying the domain's DNS host and email provider implies a usage context, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many overlapping domain-related siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AIPayGen Site Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.