dns

Dns Lookup

dns_lookup

Read-onlyIdempotent

Look up a specific DNS record type for a domain. Specify record type (e.g., 'A', 'MX', 'TXT', 'CNAME'). Returns records with TTLs and data values.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	DNS record type to query (e.g., "A", "AAAA", "MX", "NS", "TXT", "CNAME", "SOA"). Defaults to "A".
`domain`	Yes	Domain name to look up (e.g., "example.com", "mail.google.com")

Output Schema

TableJSON Schema

Name	Required	Description
`type`	Yes	DNS record type that was queried
`domain`	Yes	Domain name that was queried
`status`	Yes	DNS status code name (NOERROR, NXDOMAIN, etc.)
`records`	Yes	Array of DNS records found
`record_count`	Yes	Number of records returned

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "domain": "example.com"
+  },
+  {
+    "domain": "mail.google.com",
+    "type": "MX"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "domain": {
+      "description": "Domain name that was queried",
+      "type": "string"
+    },
+    "record_count": {
+      "description": "Number of records returned",
+      "type": "number"
+    },
+    "records": {
+      "description": "Array of DNS records found",
+      "items": {
+        "properties": {
+          "name": {
+            "description": "Full domain name of the record",
+            "type": "string"
+          },
+          "ttl_seconds": {
+            "description": "Time-to-live in seconds",
+            "type": "number"
+          },
+          "type": {
+            "description": "DNS record type (A, AAAA, MX, etc.)",
+            "type": "string"
+          },
+          "value": {
+            "description": "Record data value",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "type",
+          "ttl_seconds",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "DNS status code name (NOERROR, NXDOMAIN, etc.)",
+      "type": "string"
+    },
+    "type": {
+      "description": "DNS record type that was queried",
+      "type": "string"
+    }
+  },
+  "required": [
+    "domain",
+    "type",
+    "status",
+    "records",
+    "record_count"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 23, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "domain": "example.com"
-  },
-  {
-    "domain": "mail.google.com",
-    "type": "MX"
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "domain": {
-      "description": "Domain name that was queried",
-      "type": "string"
-    },
-    "record_count": {
-      "description": "Number of records returned",
-      "type": "number"
-    },
-    "records": {
-      "description": "Array of DNS records found",
-      "items": {
-        "properties": {
-          "name": {
-            "description": "Full domain name of the record",
-            "type": "string"
-          },
-          "ttl_seconds": {
-            "description": "Time-to-live in seconds",
-            "type": "number"
-          },
-          "type": {
-            "description": "DNS record type (A, AAAA, MX, etc.)",
-            "type": "string"
-          },
-          "value": {
-            "description": "Record data value",
-            "type": "string"
-          }
-        },
-        "required": [
-          "name",
-          "type",
-          "ttl_seconds",
-          "value"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "status": {
-      "description": "DNS status code name (NOERROR, NXDOMAIN, etc.)",
-      "type": "string"
-    },
-    "type": {
-      "description": "DNS record type that was queried",
-      "type": "string"
-    }
-  },
-  "required": [
-    "domain",
-    "type",
-    "status",
-    "records",
-    "record_count"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "domain": {
+      "description": "Domain name that was queried",
+      "type": "string"
+    },
+    "record_count": {
+      "description": "Number of records returned",
+      "type": "number"
+    },
+    "records": {
+      "description": "Array of DNS records found",
+      "items": {
+        "properties": {
+          "name": {
+            "description": "Full domain name of the record",
+            "type": "string"
+          },
+          "ttl_seconds": {
+            "description": "Time-to-live in seconds",
+            "type": "number"
+          },
+          "type": {
+            "description": "DNS record type (A, AAAA, MX, etc.)",
+            "type": "string"
+          },
+          "value": {
+            "description": "Record data value",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "type",
+          "ttl_seconds",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "DNS status code name (NOERROR, NXDOMAIN, etc.)",
+      "type": "string"
+    },
+    "type": {
+      "description": "DNS record type that was queried",
+      "type": "string"
+    }
+  },
+  "required": [
+    "domain",
+    "type",
+    "status",
+    "records",
+    "record_count"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "domain": "example.com"
+  },
+  {
+    "domain": "mail.google.com",
+    "type": "MX"
+  }
+]

First observedApr 14, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds that results include TTLs and data values, which is useful but does not disclose potential rate limits or error behavior. No contradiction; benefits slightly from annotation coverage.

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?

Two sentences, front-loaded with the action and scope, followed by examples and return fields. No filler; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering safety/idempotence, the description provides sufficient detail for a simple lookup tool. It explains purpose, record types, and return values. While it could mention the sibling 'dns_lookup_all', that is not necessary for basic usage.

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 covers 100% of parameters with detailed descriptions including the default value for 'type'. The description's record type examples (e.g., 'A', 'MX') are already present in the schema, so it adds no meaningful beyond-schema semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description starts with 'Look up a specific DNS record type for a domain' – a clear verb+resource+scope. It distinguishes itself from the sibling tool 'dns_lookup_all' by emphasizing 'specific' record type, making its intent unambiguous.

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

Usage Guidelines4/5

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

The phrase 'specific DNS record type' implies this tool is for individual lookups rather than bulk operations, but alternatives like 'dns_lookup_all' or 'reverse_dns' are not explicitly mentioned. Clear context but no explicit when-not guidance.

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

All dns tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Dns Lookup

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources