Skip to main content
Glama
Sign In
Packet Tracer Visual MCP

Packet Tracer Visual MCP

by lyf94697-droid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ptv_getCommandLog

Retrieve recent command history from Packet Tracer devices to review executed commands and debug network configurations.

Instructions

Read recent Packet Tracer command history for one device or the whole workspace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ptv_getCommandLog"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNameNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It states 'read' implying no side effects, but lacks details on what happens with an empty deviceName (returns workspace-wide history?), data freshness, or format. Minimal information beyond the basic read action.

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?

A single sentence of 14 words efficiently conveys the core purpose. It is front-loaded, but could be slightly expanded without losing conciseness to cover parameters more explicitly.

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?

Given the simple read operation with no output schema and two optional parameters, the description is minimally adequate. However, it lacks details on output format, pagination, or behavior when limit is reached, leaving gaps for an AI agent.

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 0%, so the description should compensate. It partially explains deviceName by mentioning per-device vs workspace, but does not describe the limit parameter's meaning or effect. Adds some meaning but incomplete for a 2-param tool.

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 verb 'read' and the resource 'Packet Tracer command history', with explicit scoping to 'one device or the whole workspace'. This distinguishes it from sibling tools like ptv_runShowCommands or ptv_configureIos, which have different purposes.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, limitations, or scenarios where other tools (e.g., ptv_probeDeviceApi) might be more appropriate.

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