Skip to main content
Glama

pve_sdn_vnet_ip_create

Creates an IP-to-MAC mapping in a Proxmox SDN vnet. Use to reserve an IP address for a MAC address in IPAM. Dry-run by default; set confirm=true to execute.

Instructions

MUTATION: create an IP-to-MAC mapping in a vnet (IPAM record). Dry-run by default — the PLAN cannot show a 'current' preview (this endpoint has NO GET at all — declared honestly, not fabricated). RISK_LOW: reserves a mapping; no live traffic effect until a guest's NIC resolves through it. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

NO digest support on this endpoint at all (schema-verified) — no optimistic lock possible for this family. No UNDO — revert by deleting the mapping with pve_sdn_vnet_ip_delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYesIP address to associate with the given MAC address.
macNoUnicast MAC address, XX:XX:XX:XX:XX:XX.
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?

Discloses many behaviors beyond whether it's a mutation: dry-run by default, no GET or preview, synchronous execution, return format for confirm, absence of digest support and optimistic locking, and undoing via delete. No annotations provided, so description fully covers the behavioral burden.

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?

Concise but dense with useful information, no fluff. Front-loaded with the main purpose.

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?

Covers all critical behavioral aspects: dry-run, no preview, no undo (with mention of sibling), risk level, synchrony, return format, and digest/lock limitations. Given the complexity and no annotations, this is very 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%, and the description does not add significant meaning beyond what the schema already provides. The description mentions 'confirm' for execution but no extra parameter details.

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 the action (create) and resource (IP-to-MAC mapping in a vnet), with additional context (IPAM record). Distinguishes from siblings pve_sdn_vnet_ip_delete and pve_sdn_vnet_ip_update.

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?

Discusses dry-run behavior, inability to preview (no GET), risk level, and provides alternative for undo via sibling tool. Lacks explicit when-not-to-use, but still very helpful.

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