Skip to main content
Glama
dmeiser

nextdns-mcp

by dmeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Dohlookup

dohLookup

Resolve DNS records over HTTPS for a domain using a NextDNS profile, optionally selecting profile ID and record type.

Instructions

Perform a DNS-over-HTTPS lookup using a NextDNS profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain name to look up (e.g., "adwords.google.com")
profile_idNoNextDNS profile ID. If not provided, uses NEXTDNS_DEFAULT_PROFILE.
record_typeNoDNS record type to query (default "A").A

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.5
  2. Removedv3.1.3
  3. Changed2 schema fields changedv3.0.1
    • changedInput schema / properties / profile_id / description
      Previous value: -"NextDNS profile ID (6-character alphanumeric). If not provided, uses NEXTDNS_DEFAULT_PROFILE"New value: +"NextDNS profile ID. If not provided, uses NEXTDNS_DEFAULT_PROFILE."
    • changedInput schema / properties / record_type / description
      Previous value: -"DNS record type to query. Common types:\n- A: IPv4 address (default)\n- AAAA: IPv6 address\n- CNAME: Canonical name\n- MX: Mail exchange\n- TXT: Text records\n- NS: Name servers\n- SOA: Start of authority\n- PTR: Pointer record"New value: +"DNS record type to query (default \"A\")."
  4. First observedv2.0.16

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Lookup' implies a non-mutating read, which is useful, but nothing is said about authentication requirements, rate limits, whether the profile must pre-exist, or how the default-profile fallback behaves at runtime.

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?

A single, front-loaded sentence with no waste. It is efficient, though the brevity edges toward under-specification rather than optimal conciseness.

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?

The output schema exists, so return-value explanation is not required, and the three parameters are fully covered by the schema. However, with no annotations and no usage or behavioral context, the definition is only minimally sufficient for an agent to invoke this confidently.

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 description coverage is 100%, so the schema already documents domain, profile_id (including the NEXTDNS_DEFAULT_PROFILE fallback), and record_type. The description adds no parameter meaning beyond what the schema provides, so the baseline of 3 applies.

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 (lookup) and resource (DNS-over-HTTPS via a NextDNS profile), which an agent can distinguish from the manage*/analytics siblings. It stops short of saying anything that would differentiate it from a hypothetical non-DoH DNS lookup, but the purpose is unambiguous.

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?

The description gives no indication of when to use this tool versus the sibling tools (queryAnalytics, manageLogs) or when a DoH lookup is the right approach. There are no prerequisites or exclusion conditions stated.

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

Deploy Server

Other Tools