Skip to main content
Glama

pve_sdn_prefix_list_create

Create a new SDN prefix list in Proxmox VE, optionally seeding it with entries in bulk. Uses a dry-run plan by default; confirm to execute the staged mutation.

Instructions

MUTATION: create an SDN prefix list (PENDING — inert until pve_sdn_apply).

The more granular path is create empty, then add entries one at a time via pve_sdn_prefix_list_entry_create; entries here seeds them in bulk instead. To update an existing list use pve_sdn_prefix_list_update; to remove one use pve_sdn_prefix_list_delete. Dry-run by default (returns a PLAN); confirm=True creates the pending list, returning {status, result}. RISK_LOW (staging, no live network effect).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
digestNoExpected config digest for optimistic-concurrency checking — accepted on CREATE for this endpoint (a real exception to the plane-wide 'digest never on create' convention).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
entriesNoOptional bulk seed: a list of {action, prefix, ge?, le?, seq?} entry objects, created in the SAME call. PVE validates each item server-side.
lock_tokenNoSDN cluster lock token to use for this write, if one is held.
prefix_listYesNew SDN prefix list id to create.
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?

Discloses that it is a mutation (PENDING until pve_sdn_apply), dry-run by default (returns PLAN), confirm flag to execute, RISK_LOW (staging, no live effect), and special digest behavior. With no annotations, the description fully covers behavioral traits.

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?

Description is compact with no redundant sentences. It front-loads key information (MUTATION, PENDING, inert) and uses efficient phrasing to convey workflow and alternatives.

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?

With output schema existing and no nested objects, the description explains the two-phase create-then-apply workflow, risk level, return types, and parameter purpose. It is sufficiently complete for an agent to select and invoke the tool correctly.

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 is 3. Description adds context for 'entries' (bulk seed) and 'confirm' (dry-run vs execute), and notes digest's non-standard acceptance on CREATE. This adds moderate value 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 'MUTATION: create an SDN prefix list (PENDING — inert until pve_sdn_apply)', with a specific verb and resource. It distinguishes from sibling tools like pve_sdn_prefix_list_entry_create, pve_sdn_prefix_list_update, and pve_sdn_prefix_list_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: 'The more granular path is create empty, then add entries one at a time via pve_sdn_prefix_list_entry_create; entries here seeds them in bulk instead. To update use pve_sdn_prefix_list_update; to remove use pve_sdn_prefix_list_delete.' Also explains dry-run default and confirm flag.

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