Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Set DNS configuration (unified)

tailscale_set_dns_configuration
DestructiveIdempotent

Set a tailnet's unified DNS configuration in one call, replacing nameservers, search paths, split DNS, and MagicDNS settings. Include every field to keep because omitted fields may be cleared.

Instructions

Set the unified DNS configuration for your tailnet in a single call. Replaces all DNS settings (nameservers, search paths, split DNS, MagicDNS preference). This is a replace-all endpoint: pass every top-level field you want to keep, because a field you omit may be cleared rather than left alone.

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": "tailscale_set_dns_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
dnsNoList of DNS server IP addresses
magicDNSNoWhether to enable MagicDNS
splitDnsNoMap of domain to nameserver list for split DNS, or to null to clear that domain
searchPathsNoList of DNS search domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.23.1
    • addedInput schema / properties / splitDns / additionalProperties / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / splitDns / additionalProperties / items
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / splitDns / additionalProperties / type
      Removed value: -"array"
    • changedInput schema / properties / splitDns / description
      Previous value: -"Map of domain to nameserver list for split DNS"New value: +"Map of domain to nameserver list for split DNS, or to null to clear that domain"
  2. First observedv0.13.3

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description adds important behavior beyond them: omitted top-level fields may be cleared rather than left alone. It does not discuss permissions or rate limits, but the field-clearing warning is substantive and relevant to safe invocation.

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?

The description is three focused sentences: purpose first, replacement behavior second, and the omission warning third. The second sentence slightly repeats the replacement idea, but overall it is efficient and front-loaded.

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

Completeness4/5

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

For a destructive replace-all mutation with no output schema, the description covers the key risk and the full set of DNS settings being replaced. It omits authorization requirements and leaves sibling selection implicit, so it is strong but not fully complete.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds replace-all semantics that affect how the four top-level fields must be populated. It also maps its enumerated settings to dns, searchPaths, splitDns, and magicDNS without repeating format details already in the schema.

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?

The description gives a specific verb and resource — set the unified DNS configuration for a tailnet — and the word 'unified' plus 'Replaces all DNS settings' distinguishes it from granular DNS setters in principle. It does not explicitly name the sibling alternatives, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

It signals the unified replace-all use case through 'single call' and 'Replaces all DNS settings,' implying granular setters are for narrower changes. However, it never names siblings like tailscale_set_nameservers, tailscale_set_split_dns, or tailscale_set_search_paths, nor states when to prefer them.

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