Skip to main content
Glama
madmickstar

mcp-eveng

by madmickstar

edit_lab_node

Edit an existing lab node's properties like name, icon, RAM, CPU, and more. Automatically stops the node if needed, and prevents accidental duplicate names.

Instructions

Edit an existing node by id. Only supplied fields are changed.

Covers every node field EVE-NG's own "Edit Node" dialog exposes (see get_node_template's options for the full reference) -- name, icon, image, ram/cpu/cpulimit/ethernet, console/config, canvas position, delay, the QEMU-specific fields, disable_offload, sat, eth_format/eth_name, and rdp_user/rdp_password (for rdp/rdp-tls console nodes). Deliberately excludes uuid -- an identity field EVE-NG assigns itself, not something meant to be user-edited.

Targets exactly one node -- for ram/cpu/ethernet/icon/image across every node sharing a template at once, see edit_lab_nodes_by_template. For delay specifically with bulk ordering/incrementing across many nodes, see change_node_delay.

EVE-NG requires a node to be stopped to edit it, on both PRO and Community (unlike connect_interface's wiring, which PRO allows on running nodes). This checks the node's current status first and stops it automatically if needed, before applying the edit -- you don't have to stop it yourself first.

If name is being changed and another node already has that exact name (case-insensitive), this does NOT rename it -- EVE-NG allows duplicate node names, but silently creating one seems worth avoiding by default. It returns status "confirmation_required" naming the conflicting node; call again with either a different name, or the same name plus confirm_duplicate_name=true to use it anyway.

Args: lab_path: Full path to the .unl lab file. node_id: Id of the node to edit (see list_lab_nodes). name: New name, if changing. icon: New icon filename, if changing. image: New image filename, if changing -- must be one of the template's own valid images (see get_node_template). ram: New RAM in MB, if changing. cpu: New vCPU count, if changing. cpulimit: New CPU limit toggle (0/1), if changing. ethernet: New ethernet interface count, if changing. console: New console type ("telnet"/"vnc"/"rdp"/"rdp-tls"), if changing. config: New config state ("Unconfigured"/"Saved"), if changing. left: New canvas position from the left, if changing. top: New canvas position from the top, if changing. delay: New startup delay in seconds, if changing. disable_offload: New disable-offload toggle (0/1), if changing. sat: New satellite setting, if changing. eth_format: New interface name format string, if changing. eth_name: New explicit interface names list, if changing. firstmac: New first interface MAC address, if changing. qemu_version: New QEMU version, if changing. qemu_arch: New QEMU architecture, if changing. qemu_nic: New QEMU NIC model, if changing. qemu_options: New custom QEMU options string, if changing. rdp_user: New RDP username (rdp/rdp-tls console nodes), if changing. rdp_password: New RDP password (rdp/rdp-tls console nodes), if changing. confirm_duplicate_name: Set true to use name even if another node already has it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cpuNo
ramNo
satNo
topNo
iconNo
leftNo
nameNo
delayNo
imageNo
configNo
consoleNo
node_idYes
cpulimitNo
eth_nameNo
ethernetNo
firstmacNo
lab_pathYes
qemu_nicNo
rdp_userNo
qemu_archNo
eth_formatNo
qemu_optionsNo
qemu_versionNo
rdp_passwordNo
disable_offloadNo
confirm_duplicate_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description fully covers behavioral traits: only supplied fields are changed, automatic stopping of node before edit, duplicate name behavior (returns confirmation_required), and explicit list of fields including exclusions (uuid). No contradictions.

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?

Well-structured: purpose, field list, sibling differentiation, automatic behavior, duplicate name handling, then formal Args. Every sentence adds value; no redundancy. Despite length (26 params), it is efficient and front-loaded with key info.

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?

Given 26 parameters, no annotations, and an output schema (implied), the description is complete: covers all field meanings, edge cases (duplicate names, automatic stop), and references related tools. Provides sufficient context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description includes a comprehensive Args block explaining each parameter's meaning, including constraints (e.g., image must be valid, console types listed). This adds significant context beyond the minimal schema types, fully compensating for the lack of schema descriptions.

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 'Edit an existing node by id. Only supplied fields are changed.' It specifies the resource (node) and distinguishes itself from sibling tools by explicitly naming edit_lab_nodes_by_template for bulk edits and change_node_delay for delay-specific operations.

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?

Provides explicit when-to-use (single node editing) and when-not-to-use (referring to sibling tools). Also details prerequisites (node must be stopped, but tool handles it automatically) and special cases (duplicate name handling with confirm_duplicate_name). This gives the agent clear decision support.

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/madmickstar/mcp_eveng'

If you have feedback or need assistance with the MCP directory API, please join our Discord server