Skip to main content
Glama

pve_sdn_prefix_list_entry_create

Create a pending SDN prefix-list entry with permit/deny action and CIDR prefix. Returns a dry-run plan by default; use confirm=True to stage the entry until applied.

Instructions

MUTATION: create a prefix-list entry (PENDING — inert until pve_sdn_apply).

NO digest on this endpoint (schema-verified) — unlike this same entry's own UPDATE, which does accept one. To update an existing entry use pve_sdn_prefix_list_entry_update; to remove one use pve_sdn_prefix_list_entry_delete. Dry-run by default (returns a PLAN); confirm=True creates the pending entry, returning {status, result}. RISK_LOW (staging, no live network effect).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geNoLower bound on matched prefix length (0-128).
leNoUpper bound on matched prefix length (0-128).
seqNoExplicit sequence number (1-4294967295) — omit to let PVE assign one.
actionYesMatching policy: 'permit' or 'deny'.
prefixYesCIDR network to match (e.g. 10.0.0.0/8, ::/0).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
lock_tokenNoSDN cluster lock token to use for this write, if one is held.
prefix_listYesExisting SDN prefix list id to add an entry to.
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?

Fully discloses behavior: dry-run by default, confirm=True creates pending entry, returns PLAN vs {status, result}. States 'RISK_LOW (staging, no live network effect)'. No annotations provided, so description carries full burden and excels.

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?

Very concise: four sentences covering purpose, pending nature, sibling differentiation, dry-run behavior, and risk. No wasted words; well-structured and front-loaded.

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?

Comprehensive for a complex tool with pending state and two modes. Covers lifecycle (inert until apply), default behavior, risk, and output behavior. Output schema handles return value details.

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. Description adds value by explaining confirm parameter behavior (dry-run default) and noting absence of digest. Does not repeat schema descriptions but provides context 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?

Clearly states 'MUTATION: create a prefix-list entry (PENDING — inert until pve_sdn_apply)', which is a specific verb+resource with explicit pending state. Differentiates 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?

Explicitly mentions when to use this tool vs alternatives: 'To update an existing entry use pve_sdn_prefix_list_entry_update; to remove one use pve_sdn_prefix_list_entry_delete.' Also notes the need for pve_sdn_apply to finalize.

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