Skip to main content
Glama

Get node options

proxmox_get_node_config
Read-only

Retrieve a Proxmox node's configuration options—notes, Wake-on-LAN MAC, ACME account and domains, boot delay, ballooning target, and digest—to review settings and apply safe updates.

Instructions

Get a node's own options (/etc/pve/nodes//config): notes/description, wake-on-LAN MAC, ACME account and domains, start-on-boot delay, ballooning target and location, plus the digest for safe updates.

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_config"
  }
}

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.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's job is supplementary context and it delivers: it reveals the underlying file, the exact option set returned, and that a digest is included for safe/concurrency-controlled updates. It does not explain why idempotentHint=false is set for a pure read, nor any permission or error behavior.

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 sentence, front-loaded with the verb and resource, then the file path, then a compact field enumeration. No filler or restatement of the title; every clause carries 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?

With no output schema, the description does the work of describing return contents by listing the option groups and the digest, which is sufficient for an agent to decide whether to call it. Minor gaps: no mention of what happens if the node has no config, and no explicit contrast with adjacent option-reading tools.

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 'node' parameter is fully documented in-schema, including the PROXMOX_DEFAULT_NODE fallback and the pointer to proxmox_list_nodes. The description adds nothing about the parameter, 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?

States a specific verb and resource and anchors it precisely with the backing file path (/etc/pve/nodes/<node>/config), then enumerates the exact options returned (notes, WoL MAC, ACME account/domains, start-on-boot delay, ballooning). This clearly separates it from cluster/VM/container option tools by scope, though it never names a sibling to contrast against.

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: an agent infers this is the read path for node-level options, and the trailing mention of 'the digest for safe updates' hints at a read-then-write workflow. There is no explicit statement of when to prefer this over proxmox_get_cluster_options or proxmox_get_node_status, and no prerequisites are given.

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