Skip to main content
Glama
Sign In
Proxmox VE MCP Server

Proxmox VE MCP Server

by MTDEV2312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

configure_dns_container

Set or update DNS nameserver and searchdomain for an LXC container to control name resolution and domain search.

Instructions

Update DNS nameserver and searchdomain settings for an LXC container.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node": "<node>",
      "vmid": "<vmid>"
    },
    "name": "configure_dns_container"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
vmidYes
nameserverNo
searchdomainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but it only says 'Update' without disclosing side effects, permission requirements, or whether the container must be stopped. The mutating nature is implied but not elaborated.

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 a single concise sentence with no redundancy or filler. It is appropriately front-loaded and easy to parse, though it sacrifices detail for brevity.

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

Completeness2/5

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

Given four parameters, no output schema, and no annotations, the description is far too sparse. It does not explain return values, when to use it, or the relationship to other container network tools. The tool's complexity is not matched by the description.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate. It mentions 'nameserver and searchdomain settings,' which roughly maps to the optional parameters, but it does not explain the required node and vmid parameters at all. The parameter semantics are largely unaddressed.

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 action (update) and specific resource (DNS nameserver and searchdomain settings for an LXC container). It distinguishes itself from sibling tools like configure_network_container by focusing narrowly on DNS settings.

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?

There is no guidance on when to use this tool versus alternatives such as configure_network_container. No prerequisites, exclusions, or context are provided, leaving the agent to guess when this is appropriate.

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