NextDNS-Agent-MCP

backup

Idempotent

Save a full copy of a NextDNS profile (security, privacy, parental controls, lists, rewrites, settings) before major changes so you can restore it later.

Instructions

Save a full copy of a profile (security, privacy, parental control, lists, rewrites and settings, not the logs) on this server, to put back later with restore_backup. Use it before big changes; single changes can already be undone with undo. Changes nothing in NextDNS, only writes the copy. Returns the backup ID and how many list entries it holds; backups lists all copies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "backup"
  }
}

Input Schema

Name	Required	Description	Default
`note`	No	A few words to recognise the backup later.
`profile`	No	The profile's ID or name. Leave empty for the only profile, or the default one.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedInput schema / properties / note / description

Added value: +"A few words to recognise the backup later."

addedInput schema / properties / profile / description

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

First observedv0.8.1Oct 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so safety is covered. The description adds real context beyond that: it changes nothing in NextDNS and only writes a server-side copy, and it scopes out logs. It does not discuss whether repeated calls create duplicate backups, which matters given the idempotent hint.

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?

Front-loads the core action and its scope, then follows with usage routing and return info in a logical order. It is on the longer side and the parenthetical inventory is dense, but every clause carries information.

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 annotations covering safety, a full output schema covering returns, and 100% schema coverage on parameters, the description needs only to add scope and routing — which it does completely: what is saved, what is excluded, when to use it, what alternative applies otherwise, and where to list backups.

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% and both parameters (note, profile) are fully documented in the schema, so the baseline is 3. The description adds no format or usage detail for either parameter, so it neither compensates nor detracts.

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?

States a specific verb and resource (save a full copy of a profile), enumerates exactly what is captured (security, privacy, parental control, lists, rewrites, settings) and explicitly excludes logs. It distinguishes itself from restore_backup, undo, and backups by name, so an agent can route correctly without opening a schema.

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?

Gives an explicit trigger (before big changes), an explicit exclusion with an alternative (single changes can already be undone with undo), and names the complementary tools restore_backup and backups. When-to-use, when-not, and alternatives are all present.

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