Skip to main content
Glama

pve_sdn_zone_update

Update an existing SDN zone by setting specified options or deleting keys. Dry-run returns a plan; confirm=true executes the mutation.

Instructions

MUTATION: update an SDN zone (PENDING). options sets fields; delete unsets keys.

To create a new zone use pve_sdn_zone_create; to remove one use pve_sdn_zone_delete. Dry-run by default (returns a PLAN); confirm=True stages the edit and returns {status, result}. RISK_LOW (staging; inert until pve_sdn_apply).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYesExisting SDN zone id to update.
deleteNoZone option keys to unset.
digestNoExpected config digest for optimistic-concurrency checking.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
optionsNoZone fields to set (type-specific, e.g. bridge, mtu, controller).
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
Behavior4/5

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

Discloses it's a mutation, dry-run by default, confirm=True stages the edit, and risk level LOW (inert until pve_sdn_apply). Lacks details on what happens after apply, but sufficient given no annotations.

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 concise sentences plus a short risk note, no wasted words, key information front-loaded.

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?

Covers mutation, usage, risk, and parameter roles. Has output schema, so return values are covered. Could mention dependencies on pve_sdn_apply, but overall complete.

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

Parameters4/5

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

Schema coverage is 100%, and description adds meaning by clarifying that 'options' sets fields, 'delete' unsets keys, and explains confirm behavior. Adds value 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 zone' and contrasts with create/delete, specifying verb and resource distinctly.

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

Usage Guidelines5/5

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

Explicitly says when to use this tool (update) versus alternatives (create/delete) and explains dry-run vs confirm behavior.

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