Skip to main content
Glama
Arminfx7
by Arminfx7

node

Create, list, configure, delete, and control GNS3 lab devices, including start, stop, suspend, reload, restart, and wildcard bulk actions.

Instructions

Manage GNS3 nodes (CRUD operations)

v0.47.0: CRUD-style consolidation of create_node, delete_node, and set_node. v0.40.0: Enhanced with wildcard and bulk operation support.

Actions: - list: List nodes in a project - create: Create new node from template at specified coordinates - delete: Delete node from project (WARNING: destructive, cannot be undone) - set: Configure node properties and/or control state (supports wildcards/bulk)

Wildcard Patterns (for 'set' and 'delete'): - Single node: "Router1" - All nodes: "" - Prefix match: "Router" (matches Router1, Router2, RouterCore) - Suffix match: "*-Core" (matches Router-Core, Switch-Core) - Character class: "R[123]" (matches R1, R2, R3) - JSON array: '["Router1", "Router2", "Switch1"]'

Validation Rules: - name parameter requires node to be stopped - Hardware properties (ram, cpus, hdd_disk_image, adapters) apply to QEMU/IOU/Docker/Dynamips - For IOU nodes, 'adapters' maps to 'ethernet_adapters' automatically - ports parameter applies to ethernet_switch nodes only - state_action values: start, stop, suspend, reload, restart

Returns: Single node: Status message Multiple nodes: BatchOperationResult JSON with per-node success/failure

Examples: # List nodes in project >>> node(action="list", project_id="abc-123") >>> node(action="list", project_id="abc-123", format="json")

# Create new node
>>> node(action="create", template_name="Alpine Linux", x=100, y=200)
>>> node(action="create", template_name="Cisco IOSv", x=300, y=400, node_name="R1", properties={"ram": 1024})

# Delete node
>>> node(action="delete", node_name="Router1")

# Start all nodes
>>> node(action="set", node_name="*", state_action="start")

# Stop all routers
>>> node(action="set", node_name="Router*", state_action="stop")

# Configure node properties
>>> node(action="set", node_name="R1", x=100, y=200, ram=2048)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX coordinate (top-left corner of node icon)
yNoY coordinate (top-left corner of node icon)
zNoZ-order layer for overlapping nodes
ramNoRAM in MB (QEMU nodes only)
cpusNoNumber of CPUs (QEMU nodes only)
nameNoNew name (REQUIRES node stopped)
portsNoNumber of ports (ethernet_switch nodes only)
slot1NoDynamips c3600/c3725 network module for slot 1, for example NM-4T
actionYesAction: 'list' (list nodes), 'create' (new node), 'delete' (remove node), or 'set' (configure/control node)
formatNoOutput format: 'table' (default) or 'json' (for 'list' action)table
lockedNoLock position to prevent GUI moves
adaptersNoNetwork adapters (QEMU: adapters, IOU: ethernet_adapters)
parallelNoExecute operations concurrently (default: True for start/stop/suspend)
node_nameNoNode name, wildcard pattern ('*', 'Router*', 'R[123]'), or JSON array ('["R1","R2"]'). Required for 'delete' and 'set'
compute_idNoCompute server ID (for 'create')local
project_idNoProject ID (required for 'list')
propertiesNoOverride template properties for 'create' (e.g., {'ram': 512})
adapter_typeNoVirtualBox only: adapter model, for example PCnet-FAST III (Am79C973)
console_typeNoConsole type: telnet/vnc/spice
state_actionNoState control action for 'set': 'start' (boot), 'stop' (shutdown), 'suspend' (pause), 'reload' (reboot), 'restart' (stop then start)
template_nameNoTemplate name (required for 'create', e.g., 'Alpine Linux', 'Cisco IOSv')
hdd_disk_imageNoHDD disk image path (QEMU nodes only)
use_any_adapterNoVirtualBox only: allow the VM to use any available network adapter

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.54.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it flags delete as destructive and irreversible, states that renaming requires a stopped node, documents bulk/wildcard execution and the parallel default, and notes per-node success/failure returns for batch operations. It omits auth/permission requirements and error behavior, keeping it below 5.

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 long but well sectioned (Actions, Wildcards, Validation, Returns, Examples) with the core purpose front-loaded. Some example redundancy (multiple start/stop variants) slightly exceeds what is needed.

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?

For a 23-parameter multi-action tool this is nearly complete: action semantics, wildcard grammar, validation constraints, and return shapes are all covered. An output schema exists so the Returns section is a bonus, not a necessity, and the remaining gap is error/auth behavior.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real value beyond the schema: wildcard pattern syntax for node_name, JSON array input form, the IOU 'adapters' → 'ethernet_adapters' mapping, and worked examples of properties overrides.

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 opens with a specific verb+resource ('Manage GNS3 nodes') and enumerates the four CRUD actions with one-line semantics each. An agent can distinguish this tool from siblings like link, project, and node_file without opening the schema.

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?

Each action is described with its purpose ('delete: Delete node from project'), and the validation/returns sections imply when each action applies. However, there is no explicit guidance on when to prefer this tool over siblings such as node_file or link for node-adjacent operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.