Skip to main content
Glama

pve_sdn_zone_create

Stage a new SDN zone for later application. Dry-run returns a plan; confirm=true creates the pending zone.

Instructions

MUTATION: create an SDN zone (PENDING — inert until pve_sdn_apply, NOT applied here).

zone_type is simple/vlan/qinq/vxlan/evpn/faucet; options carries type-specific params. To update an existing zone use pve_sdn_zone_update; to remove one use pve_sdn_zone_delete. Dry-run by default (returns a PLAN); confirm=True creates the pending zone, returning {status, result}. RISK_LOW (staging, no live network effect).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYesNew SDN zone id to create.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
optionsNoType-specific zone options (e.g. bridge, mtu, controller).
zone_typeYesZone type: simple, vlan, qinq, vxlan, evpn, or faucet.
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
Behavior5/5

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

No annotations provided, but the description fully discloses the staged mutation, pending nature, dry-run behavior, and risk level. All behavioral traits are surfaced clearly without contradictions.

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?

Concise yet comprehensive with a clear structure: mutation label, pending behavior, key parameters, sibling references, and risk. Front-loaded with essential info, but slightly verbose. Still efficient.

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?

For a complex mutation tool with 6 parameters and a staged workflow, the description covers core behavior, parameter semantics, related tools, and risk. Output schema exists, so return value explanation is unnecessary.

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%, so baseline 3. The description adds value by explaining zone_type allowed values, options as type-specific, and confirm as dry-run toggle. It enriches understanding beyond the 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 the tool creates an SDN zone and explains the pending/staging behavior. It distinguishes from siblings by referencing pve_sdn_zone_update and pve_sdn_zone_delete.

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?

Provides clear context for when to use (create zone) and mentions alternatives (update/delete). Explains the dry-run default and confirm flag, guiding the agent on execution. Lacks explicit when-not-to-use but is sufficiently informative.

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