Skip to main content
Glama

pve_sdn_prefix_list_entry_update

Update an existing SDN prefix list entry. Returns a dry-run plan by default; use confirm=true to apply the change.

Instructions

MUTATION: update a prefix-list entry (PENDING). To create a new entry use pve_sdn_prefix_list_entry_create; to remove one use pve_sdn_prefix_list_entry_delete. Dry-run by default (returns a PLAN); confirm=True stages the edit and returns {status, result}. RISK_LOW (staging).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geNoNew lower bound on matched prefix length (0-128).
leNoNew upper bound on matched prefix length (0-128).
seqNoNew sequence number (1-4294967295).
actionNoNew matching policy: 'permit' or 'deny'.
deleteNoField names to unset — only 'le', 'ge', 'seq' are valid values on this endpoint.
digestNoExpected config digest for optimistic-concurrency checking — accepted here (unlike this same entry's own CREATE, which has none).
prefixNoNew CIDR network to match.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
entry_idYesOPAQUE entry path token (the schema's {url_seq}) — capture from a prior list/get read.
lock_tokenNoSDN cluster lock token to use for this write, if one is held.
prefix_listYesExisting SDN prefix list id.
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. Clearly states it's a mutation, dry-run by default, confirm flag stages edit, and risk level low. Does not detail idempotency or side effects beyond staging.

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 sentences covering purpose, workflow, risk, and sibling references. Efficient and 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 purpose, alternatives, workflow, and risk. Does not mention how to obtain entry_id or prefix_list, but output schema and parameter descriptions fill some gaps.

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 no additional meaning to parameters beyond what schema already provides.

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?

Description clearly states the tool updates a prefix-list entry and distinguishes it from create and delete siblings, using specific verbs and resource references.

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 explicit when to use this tool vs alternatives (create/delete) and explains dry-run vs confirm workflow. Could add prerequisite like fetching entry_id from list/get.

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