Skip to main content
Glama
Sign In
pt-mcp

pt-mcp

by kiskander
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Open a Network File

open_network_file
Destructive

Loads a Cisco Packet Tracer .pkt or .pka file by absolute path and returns the result code; warns that it replaces the current network, so confirm before opening.

Instructions

Open a .pkt (network) or .pka (activity) file. Returns Packet Tracer's result code.

CRITICAL: Replaces the open network; unsaved changes may be lost. Confirm with the user first.

Examples:

  • "Open ~/labs/ospf.pkt"

  • "Load the activity file I downloaded"

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": {
      "path": "<path>"
    },
    "name": "open_network_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to a .pkt/.pka file on the Packet Tracer host

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior5/5

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

The annotations already flag destructiveHint=true, and the description adds the concrete consequence beyond the flag: the open network is replaced and unsaved changes may be lost, plus a required user-confirmation step. That is exactly the extra context the annotation cannot convey, and it is consistent with the destructive hint.

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 destructive warning is front-loaded and clearly separated from the functional sentence. The two examples are short but partly redundant with the parameter description, adding some length without much new information.

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?

For a single-parameter destructive tool with an output schema (so return values need no explanation) and full annotation coverage, the description supplies everything an agent needs: accepted file types, the destructive consequence, and the confirmation requirement.

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 coverage is 100% and the single path parameter is already documented as an absolute path to a .pkt/.pka file, so the schema carries the burden. The examples add mild format guidance but never clarify whether tilde paths are accepted, and the '~' example mildly conflicts with the schema's 'absolute path' wording.

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?

States a specific verb (open) and resource (a .pkt/.pka network or activity file), with scope that clearly distinguishes it from save_network_file and create_new_network. The added note that it returns Packet Tracer's result code further pins down what the caller gets.

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?

Gives explicit preconditions (confirm with the user first, because the currently open network is replaced) and illustrates with two realistic invocation examples. It stops short of naming an alternative sibling such as create_new_network or save_network_file for the case where the user doesn't want to replace the current file.

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

Deploy Server

Other Tools