NextDNS-Agent-MCP

profile

Read-only

Show a single NextDNS configuration as text: security, privacy, parental control, denylist, allowlist, rewrites, settings, and DNS setup to inspect it before making changes; read-only.

Instructions

Show one profile's configuration as text: security, privacy, parental control, denylist, allowlist, rewrites, settings and setup (the DNS addresses devices use). Use it to see how a profile is set up before changing it; use compare_profiles to set two side by side and check_domain to know if one domain is blocked. Changes nothing. Without section, long lists are cut short; an unknown section is refused with the valid ones.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`profile`	No	The profile's ID or name. Leave empty for the only profile, or the default one.
`section`	No	Show just one part in full: security, privacy, parental_control, denylist, allowlist, rewrites, settings or setup. Empty shows a summary with long lists cut short.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedInput schema / properties / profile / description

Added value: +"The profile's ID or name. Leave empty for the only profile, or the default one."

addedInput schema / properties / section / description

Added value: +"Show just one part in full: security, privacy, parental_control, denylist, allowlist, rewrites, settings or setup. Empty shows a summary with long lists cut short."

First observedv0.8.1Oct 20, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the `readOnlyHint`, the description adds crucial behavioral context, such as confirming 'Changes nothing,' stating that 'long lists are cut short,' and clarifying that unknown sections are rejected.

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?

The description is dense but highly efficient. It front-loads the core function, provides key usage instructions, and covers necessary behavioral warnings without being verbose.

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 the existence of an output schema, the description is complete. It covers the operational constraints (read-only, list truncation) and usage context required for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While schema coverage is 100%, the description provides vital domain knowledge by listing the valid values for the 'section' parameter (e.g., security, privacy, denylist), grounding the abstract string inputs.

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 the purpose is to 'Show one profile's configuration' and lists the specific configuration types (security, privacy, etc.), distinguishing it from other profile-related tools.

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?

It explicitly guides the user to the correct tool for specific tasks: use this tool to 'see how a profile is set up before changing it,' and directs users to 'compare_profiles' or 'check_domain' for alternative needs.

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