PNETLab MCP Server

push_config

Push a startup configuration to a node that is stored and loaded on next boot. Include 'vtp mode transparent' before VLAN definitions for IOL L2 switches to persist VLANs.

Instructions

Push a startup-config to a node (stored; loads on next boot). For IOL L2 switches, include 'vtp mode transparent' before 'vlan N' or the VLAN won't persist. VPCS nodes ignore startup-config — configure their IP on the live console instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lab_path": "<lab_path>",
      "node_id": "<node_id>",
      "config": "<config>"
    },
    "name": "push_config"
  }
}

Input Schema

Name	Required	Description	Default
`config`	Yes
`node_id`	Yes
`lab_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Despite no annotations, the description discloses key behaviors: config is stored and loads on next boot (delayed effect), IOL L2 switches require specific command order, VPCS nodes ignore startup-config. This fully informs the agent of consequences.

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?

Three sentences, each serving a distinct purpose: main action, IOL caveat, VPCS caveat. Front-loaded with purpose, no redundant phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Provides important behavioral context and usage caveats, but lacks any parameter descriptions. Given the tool has 3 required parameters and an output schema, the description is incomplete without parameter guidance.

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

Parameters1/5

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

With 0% schema description coverage, the description must explain parameters, but it does not. No information about what the config string should contain, how to specify node_id, or format of lab_path. This is a critical gap.

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 action 'push a startup-config' and the target resource 'to a node'. It distinguishes from sibling tools like export_config or get_node_config by specifying it's for pushing a startup config that loads on next boot.

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 guidance on when to use (push startup config) and when not to use (VPCS nodes ignore startup-config). Also gives a critical workaround for IOL L2 switches regarding 'vtp mode transparent' before VLAN entries.

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