Skip to main content
Glama

pve_sdn_vnet_ip_update

Update an IP-to-MAC mapping in a Proxmox SDN vnet. Optionally associate a VMID. Use confirm=true to apply; dry-run by default.

Instructions

MUTATION: update an IP-to-MAC mapping in a vnet. Dry-run by default — no 'current' preview possible (no GET on this endpoint at all). RISK_LOW. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

vmid is accepted on THIS verb only (not create/delete — schema-verified). NO digest support on this endpoint at all. No UNDO — revert by updating it back to its prior mac/vmid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYesIP address of the mapping to update.
macNoNew unicast MAC address, XX:XX:XX:XX:XX:XX.
vmidNoGuest VMID/CTID to associate with the mapping for tracking/audit purposes (PUT-only — not accepted on create/delete).
vnetYesSDN vnet name.
zoneYesSDN zone the vnet belongs to.
confirmNoSet True to execute the mutation; False (default) only returns a dry-run PLAN.
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?

With no annotations provided, the description fully discloses behavioral traits: mutation, dry-run behavior, no GET endpoint, risk level (RISK_LOW), synchronous execution, output format, lack of digest support, and irreversible nature. This is comprehensive and exceeds the burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured with clear bullet points and concise sentences. It packs essential information without unnecessary verbosity, though slight reorganization could improve readability.

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 presence of an output schema (indicated by context signals), the description covers the main behavior, parameters, and constraints effectively. It could mention prerequisites like vnet/zone existence, but overall it is adequately 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 description coverage is 100%, so the description adds marginal value beyond the schema. It does provide extra context for `vmid` (PUT-only) and `confirm` (dry-run vs execution), but most parameter details are already in 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?

Description clearly states 'MUTATION: update an IP-to-MAC mapping in a vnet' with specific verb and resource. It distinguishes from siblings by noting that `vmid` is accepted only on this verb, not on create/delete.

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?

Description explains dry-run default, synchronous execution, and the effect of `confirm` parameter. It also notes the absence of a GET preview and undo capability, providing some guidance on when to use. However, it does not explicitly outline scenarios for choosing this tool over others.

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