Skip to main content
Glama
madmickstar

mcp-eveng

by madmickstar

connect_interface

Connect a node interface to another node or to an existing network, automatically selecting an available interface if none specified.

Instructions

Connect one node's interface to another node, or to an existing network.

Exactly one target is required: target_node_id (connects directly to another node -- EVE-NG has no dedicated "connect two nodes" API endpoint, so this creates a new bridge network behind the scenes and wires both nodes' interfaces to it, exactly what EVE-NG's own GUI does when you draw a line directly between two node icons; it renders as a plain line, not a separate network icon, because it ends up with exactly two node endpoints) or network_id/network_name (connects to a network you already created yourself, e.g. via add_lab_network -- this one stays visible on the canvas as its own icon, same as wiring a cloud/bridge manually in the GUI).

interface/target_interface accept an interface name (e.g. "Gi0/0"), a 0-based index, or can be omitted to auto-pick that node's first available (currently unconnected) ethernet interface. Scoped to ethernet interfaces only.

EVE-NG PRO allows wiring interfaces on running nodes; Community requires every node involved to be stopped first. This checks the server's edition automatically and, on Community only, stops any running node(s) involved before wiring them -- same stop-if-needed behavior as edit_lab_node.

Args: lab_path: Full path to the .unl lab file. node_id: Id of the node whose interface is being connected. interface: Which interface on node_id -- name, index, or omit to auto-pick the first available one. target_node_id: For a node-to-node connection: id of the other node. target_interface: Which interface on target_node_id -- name, index, or omit to auto-pick the first available one. network_id: For a node-to-network connection: the network's id. network_name: For a node-to-network connection: the network's exact name (case-insensitive), if you don't already know its id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYes
lab_pathYes
interfaceNo
network_idNo
network_nameNo
target_node_idNo
target_interfaceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries full burden. It transparently discloses that node-to-node connections are implemented via a hidden bridge network (mimicking GUI behavior), and that on Community edition, nodes are automatically stopped before wiring. The description also mentions scoping to ethernet interfaces and auto-pick behavior.

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?

The description is well-structured into paragraphs and a parameter list, but it is moderately lengthy. Most sentences add value, though some parenthetical clarifications could be slightly tightened. Overall, it remains clear and front-loaded with the core behavior.

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 7 parameters, no annotations, and moderate complexity (mutual exclusivity, auto-pick, edition differences), the description is complete. It covers all edge cases (auto-pick, community vs. PRO, visual differences) and provides enough context for an agent to invoke the tool correctly without needing to consult external documentation.

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 description coverage is 0%, so the description must fully explain all 7 parameters. It does so comprehensively: explaining lab_path, node_id, interface/target_interface (name, index, or omit), and the exclusive mutual exclusion between target_node_id and network_id/network_name pairs, including context on why they differ in canvas appearance.

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 the tool connects one node's interface to another node or to an existing network. It distinguishes between two modes (node-to-node vs. node-to-network) and explains the visual/canvas behavior, differentiating it from sibling tools like add_lab_network or edit_lab_node.

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?

The description explicitly explains the two usage paths (target_node_id vs. network_id/network_name) and provides detailed context on when to use each. It also covers auto-picking interfaces, EVE-NG edition differences (PRO vs. Community) with stop-if-needed behavior, referencing sibling-like behavior from edit_lab_node for clarity.

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