Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

network_dns

Resolve DNS records (A, AAAA, MX, NS, TXT, CNAME, PTR, SOA) for any domain or IP. Queries a public resolver to retrieve and display record details.

Instructions

DNS Lookup (NSLookup / Dig). Run a live DNS record lookup for a domain or IP, resolving A, AAAA, MX, NS, TXT, CNAME, PTR, or SOA records by sending an outbound query to a public resolver (default 8.8.8.8). Use this for forward and record-type lookups on a hostname; use network_reverse_dns to turn an IP into a hostname via PTR, or network_dns_propagation to compare a record across many global resolvers. NOT read-only and NOT idempotent: it reaches the public DNS system and results vary by resolver, caching, and TTL. Rate-limited (20 requests/minute for anonymous callers). Returns an array of records with name, type, ttl, value, and per-type details (MX priority, SOA serial/refresh/retry/expire).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesDomain name or IP address to resolve (for example example.com or 8.8.8.8). Validated as a hostname or IP; must not be blank.
recordTypeNoDNS record type to query. Defaults to A (IPv4). PTR reverses an IPv4 host into in-addr.arpa form automatically.A
dnsServerNoResolver IP used for the lookup. Defaults to Google Public DNS (8.8.8.8). Honored when a remote worker performs the query.8.8.8.8
worker_idNoOptional registered healthy worker peer ID. Omit to use the default master-server behavior.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the lookup completed.
hostNoThe queried domain or IP, echoed back.
recordTypeNoThe record type that was queried.
dnsServerNoThe resolver IP used for the query.
recordsNoMatched DNS records (empty when none exist or the query failed).
authorityNoAuthority-section records, or null when not provided.
additionalNoAdditional-section records, or null when not provided.
timestampNoISO 8601 time the response was generated.
Behavior5/5

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

Explicitly states it is NOT read-only and NOT idempotent, results vary by resolver/caching/TTL, and rate-limited. This goes beyond annotations (which set hints) to provide behavioral context.

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?

Description is concise, front-loaded with primary action, and includes all necessary details in a well-structured manner. No unnecessary sentences.

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?

Given output schema exists, description covers return format. It addresses side effects, rate limits, and comparison to siblings, making it complete for its complexity.

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%, so baseline 3. The description adds minor context (default resolver, PTR auto-reverse) but does not significantly enhance parameter understanding beyond the schema.

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?

The description clearly states it performs DNS lookups resolving A, AAAA, MX, etc. records. It distinguishes from sibling tools network_reverse_dns and network_dns_propagation by explicitly comparing usage.

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

Usage Guidelines5/5

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

Explicitly states when to use (forward/record-type lookups) and when not (use network_reverse_dns for IP->hostname, network_dns_propagation for global prop). Also mentions rate limits (20 req/min) guiding agent expectations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server