Skip to main content
Glama

Get SDN status on nodes

proxmox_get_sdn_status
Read-only

Retrieve live SDN status per node, zone, and vnet to verify configuration after applying changes or locate nodes where a zone reports an error.

Instructions

Show the live SDN state on nodes: each zone's status (available/pending/error) per node and the status of the vnets in it. Use it after proxmox_apply_sdn to confirm the configuration came up, or to find nodes where a zone is in error.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoOnly this node (default all online nodes)
zoneNoOnly this zone
vnetsNoInclude per-vnet status inside each zone (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.9/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 safety is covered without description help. The description adds that this is live/observed state used for verification and error-finding, and the schema-level default of 'all online nodes' clarifies scope. It does not state that results are a point-in-time snapshot with no caching, nor how errors are surfaced, so added behavioral value is moderate.

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?

Two sentences, both earning their place: the first defines the returned state, the second defines when to reach for it. It is front-loaded and free of filler.

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?

There is no output schema, so the description's sketch of the response (zone status per node, vnet statuses) carries the return-value burden, and it does so adequately. With read-only behavior covered by annotations and all three optional parameters documented in the schema, an agent has enough to call this correctly.

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%, so each parameter (node, zone, vnets) is already documented, which sets the baseline at 3. The description's mention of 'each zone's status per node' and 'the status of the vnets in it' loosely aligns with the node/zone/vnets parameters but adds no filtering syntax or interaction detail beyond 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 ('Show the live SDN state on nodes') and spells out the payload: per-node zone status values (available/pending/error) and the status of vnets inside each zone. The word 'live' plus the emphasis on per-node state implicitly separates it from rollout/diff-style siblings such as proxmox_get_sdn_pending_diff, though no sibling is named directly.

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

Usage Guidelines4/5

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

It gives concrete when-to-use guidance: after proxmox_apply_sdn to verify configuration came up, or to locate nodes where a zone is in error. It does not name a when-not condition or point to an alternative sibling (e.g. pending-diff or object lookup) for the pre-apply case, so it stops short of a full routing statement.

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