Skip to main content
Glama

pve_sdn_route_map_entry_update

Update an existing SDN route-map entry identified by its order position. Dry-run returns a plan; set confirm=True to stage the change.

Instructions

MUTATION: update a route-map entry (PENDING). To create a new entry use pve_sdn_route_map_entry_create; to remove one use pve_sdn_route_map_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
callNoNew route-map id to invoke as a sub-routine.
matchNoReplacement array of {key, value} match-clause objects.
orderYesEntry position to update (0-65535, required — identifies WHICH entry; not itself changeable via this call).
actionNoNew matching policy: 'permit' or 'deny'.
deleteNoField names to unset — only 'set', 'match', 'call', 'exit-action' are valid values on this endpoint (NOT action or order).
digestNoExpected config digest for optimistic-concurrency checking.
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.
exit_actionNoReplacement {key, value} exit-action object.
set_clausesNoReplacement array of {key, value} set-clause objects (wire key 'set').
route_map_idYesExisting SDN route map 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?

With no annotations, the description takes on full burden. It discloses the mutation is staged (RISK_LOW), describes dry-run default returning a PLAN, and confirm=True staging edits to return status/result. This is transparent and sufficient for safe usage, though it could mention success/failure more explicitly.

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?

Three concise sentences front-load the mutation type and resource, then add sibling guidance and behavioral details. No extraneous text; every sentence serves a purpose.

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?

Given the 12-parameter complexity and presence of an output schema, the description covers the essential aspects: mutation nature, staging behavior, and return values. It could benefit from a brief mention of the broader SDN context, but it is largely complete.

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%, so baseline is 3. The description does not add new parameter-specific info beyond what each parameter's description already provides (e.g., confirm's behavior is repeated). No additional semantic value is contributed.

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 it updates a route-map entry, distinguishing it from sibling tools (create, delete) by name. The verb 'update' and resource 'route-map entry' are specific and unambiguous.

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?

It explicitly directs users to sibling tools for creation and deletion, and explains the dry-run vs. confirm behavior. While it lacks explicit 'when not to use' details, the provided alternatives and staging context are clear.

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