Skip to main content
Glama
Sign In
Packet Tracer Visual MCP

Packet Tracer Visual MCP

by lyf94697-droid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ptv_addLink

Create a link between two existing Packet Tracer interfaces to connect network devices.

Instructions

Create one link between two existing Packet Tracer interfaces.

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": {
      "fromDevice": "<fromDevice>",
      "toDevice": "<toDevice>"
    },
    "name": "ptv_addLink"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromDeviceYes
fromInterfaceNoauto
toDeviceYes
toInterfaceNoauto
linkTypeNoauto
autoAssignPortsNo
autoFallbackNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the operation ('Create one link') without mentioning side effects, error conditions, or behavior of parameters like autoAssignPorts and autoFallback. Minimal disclosure for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence (11 words), which is appropriate in length but lacks substantive information. It is concise but at the expense of clarity on parameters and behavior.

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

Completeness1/5

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

Given the tool has 7 parameters, no output schema, and no annotations, the description is severely inadequate. It does not cover return values, error handling, or parameter dependencies, leaving the agent with insufficient context to use the tool correctly.

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?

Schema description coverage is 0%, and the description adds no meaning to any of the 7 parameters. It does not explain the roles of fromDevice, toDevice, fromInterface, toInterface, linkType, autoAssignPorts, or autoFallback. The agent must rely solely on parameter names.

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 ('Create one link'), the resource ('link'), and the context ('between two existing Packet Tracer interfaces'). It distinguishes from siblings like ptv_addDevice or ptv_addDevicesTimeline, which involve adding different entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, nor any prerequisites (e.g., devices and interfaces must exist). The description implies usage but does not help the agent decide between this and other link-related tools like ptv_addLinksTimeline.

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