Skip to main content
Glama

pve_sdn_subnet_update

Update an SDN subnet in Proxmox VE with dry-run planning; confirm to stage changes.

Instructions

MUTATION: update an SDN subnet (PENDING). subnet is the id from pve_sdn_subnet_list.

To create a subnet use pve_sdn_subnet_create; to remove one use pve_sdn_subnet_delete. Dry-run by default (returns a PLAN); confirm=True stages the edit and returns {status, result}. RISK_LOW (staging).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vnetYesSDN vnet name the subnet belongs to.
deleteNoSubnet option keys to unset.
digestNoExpected config digest for optimistic-concurrency checking.
subnetYesSubnet id (CIDR) from pve_sdn_subnet_list to update.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
optionsNoSubnet fields to set (gateway, snat, dhcp, etc).
lock_tokenNoSDN cluster lock token to use for this write, if one is held.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided; description adds mutation label, dry-run default, confirm behavior, and risk level. However, it doesn't disclose error handling, reversibility, or concurrency implications.

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?

Efficiently structured with clear labels (MUTATION) and no extraneous content; every sentence provides actionable information.

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

Completeness3/5

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

Given the 8 parameters and presence of output schema, the description minimally covers key behaviors (dry-run, confirm) but omits explanation of digest, delete, and lock_token. Adequate but not thorough.

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 baseline 3; description adds context for `subnet` and `confirm`, but other parameters like `delete`, `digest`, `options`, `lock_token` are not explained beyond schema.

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 'update an SDN subnet' and identifies the resource via `subnet` as the id from the list tool, distinguishing it from create and delete siblings.

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?

Explicitly mentions create/delete siblings and explains the dry-run vs. confirm behavior, though it doesn't specify prerequisites or when not to use (e.g., if subnet doesn't exist).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server