Packet Tracer Visual MCP

by lyf94697-droid

Overview Schema Source Related Servers Discussions Admin

Python

Local

ptv_addLinksTimeline

Add network links sequentially with adjustable delays to record topology wiring step by step.

Instructions

Create links one by one with a short delay, optimized for recording a topology being wired.

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": {
      "links": "<links>"
    },
    "name": "ptv_addLinksTimeline"
  }
}

Input Schema

Name	Required	Default
`links`	Yes
`delayMs`	No
`qualityMode`	No	fast-safe
`maxRetries`	No
`retryDelayMs`	No
`settleMs`	No
`minSpacing`	No
`autoAssignPorts`	No
`autoFallback`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 18, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Without annotations, the description must convey behavioral traits. It only mentions sequential creation with a delay, but does not disclose behavior around retries, quality modes, or error handling.

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 sentence, concise and front-loaded. However, it sacrifices necessary detail, making it under-specified for a tool with many parameters.

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 9 parameters, no annotations, and no output schema, the description is far too minimal. It lacks information on return values, error handling, and parameter configurations.

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 parameter. It only hints at delay without linking to the delayMs parameter or explaining others.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it creates links sequentially with delay, optimized for recording topology wiring, clearly identifying the verb and resource and distinguishing from a bulk add.

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?

The description implies usage for recording wiring sequences but provides no explicit guidance on when to use this vs. ptv_addLink or other siblings, nor any exclusions.

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