Skip to main content
Glama

pve_sdn_vnet_create

Creates a new SDN virtual network (vnet) in a specified zone with optional tag, alias, and vlanaware settings. Dry-run by default; confirm to stage the creation for later application.

Instructions

MUTATION: create an SDN vnet in a zone (PENDING). options carries tag/alias/vlanaware/etc.

To update an existing vnet use pve_sdn_vnet_update; to remove one use pve_sdn_vnet_delete. Dry-run by default (returns a PLAN); confirm=True creates the pending vnet and returns {status, result}. RISK_LOW (staging; inert until pve_sdn_apply).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vnetYesNew SDN vnet name to create.
zoneYesSDN zone id the vnet belongs to.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
optionsNoVnet options such as tag, alias, and vlanaware.
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?

No annotations provided, so description carries full burden. It discloses mutation, pending state, dry-run, and inertness until pve_sdn_apply. Lacks details on failure cases or exact plan content, but overall transparent.

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?

Four succinct sentences, each earning its place: purpose, sibling reference, dry-run/confirm behavior, risk. Front-loaded and 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?

Given output schema exists (return values documented elsewhere), description covers creation flow, staging, risk, and sibling tools. Complete for its complexity.

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%, baseline 3. Description adds 'options carries tag/alias/vlanaware/etc.' but does not deeply expand beyond schema. Adequate but not exceptional.

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?

Clearly states it is a mutation that creates an SDN vnet in a zone, with explicit mention of 'PENDING' indicating staged operation. Distinguishes from sibling tools for update and delete.

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?

Provides explicit guidance: use for creation, use pve_sdn_vnet_update for updates and pve_sdn_vnet_delete for removal. Also explains dry-run default and confirm=True behavior, plus risk level.

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