Skip to main content
Glama

Get node DNS settings

proxmox_get_node_dns
Read-only

Retrieve a Proxmox node's DNS resolver settings, including the search domain and up to three name servers, to verify or troubleshoot node DNS configuration.

Instructions

Get a node's DNS resolver settings: search domain and up to three name servers.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description's contribution is the return shape (search domain plus up to three nameservers), which matters since there is no output schema, but it says nothing about auth, failure modes, or what happens when DNS is unconfigured.

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?

One tight sentence that front-loads the resource and then the returned fields; there is no filler and nothing that could be cut without losing information.

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 low-complexity read tool with full schema coverage and explicit read-only annotations, the description covers the essential gap (what the call returns). It would only be stronger if it noted behavior when DNS is unset or whether the values are read live from the node.

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 the single optional 'node' parameter already documents its default via PROXMOX_DEFAULT_NODE and points at proxmox_list_nodes. The description adds no further meaning about the node argument, so the baseline 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?

The description gives a specific verb and resource ('Get a node's DNS resolver settings') and even enumerates the returned contents (search domain, up to three name servers), which distinguishes it from adjacent node getters like hosts or network. It stops short of explicitly contrasting itself with the closest sibling, proxmox_get_node_hosts, so a 4 rather than a 5.

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?

Usage is only implied by the resource scope: read this when you need DNS resolver configuration for a node. There is no statement of when to prefer an alternative, no prerequisites, and no exclusions, which is acceptable for a simple single-purpose read but leaves guidance thin.

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