Skip to main content
Glama
Sign In
pt-mcp

pt-mcp

by kiskander
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Send a Simple PDU (ICMP)

send_simple_pdu

Create an ICMP echo PDU between two Packet Tracer devices and return its index, so you can step through simulation hops and inspect ARP events.

Instructions

Create a Simple PDU (the envelope tool: an ICMP echo) from one device to another. In Simulation mode, step_simulation then moves it hop by hop and get_simulation_events shows where it went -- including any ARP it triggers. Returns the PDU's index in the user-created PDU list.

Examples:

  • "Send a ping PDU from PC1 to the server and watch it"

  • "Show me how ARP works between PC1 and R1"

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": {
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "send_simple_pdu"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesDevice display name as shown in Packet Tracer (e.g. 'Router0', 'PC1')
destinationYesDevice display name as shown in Packet Tracer (e.g. 'Router0', 'PC1')

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/safety profile is covered. The description adds that the PDU is queued in a 'user-created PDU list' and returns its index, plus that ARP may be triggered, which is useful. It still leaves ambiguous what happens outside Simulation mode (does the PDU actually traverse the network?) — a meaningful gap for this tool.

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?

Core behavior is front-loaded in the first sentence, with the simulation workflow and examples following as supplementary detail. The examples and the 'envelope tool' aside are slightly discursive but still earn their place by disambiguating terminology.

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

Completeness4/5

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

An output schema exists, so return values needn't be explained, and the description still helpfully notes the PDU index. Given the two well-documented parameters and the simulation workflow hint, an agent has enough to call it correctly; only the realtime-mode behavior is left unclear.

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 both parameters already document that they take Packet Tracer display names. The description adds no further semantics (no mention that source/destination must exist, be powered on, or be of compatible types), so baseline 3 applies.

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?

Names a specific verb and resource ('Create a Simple PDU (ICMP echo) from one device to another') and clarifies it is the envelope/ping tool. It distinguishes itself from simulation siblings by naming step_simulation and get_simulation_events, though it never contrasts with verify_connectivity, which an agent could plausibly confuse it with.

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 a concrete workflow for Simulation mode (create, then step_simulation, then get_simulation_events) and two example phrasings showing when to reach for it. It doesn't state exclusions — e.g. whether it can be used in realtime mode or when verify_connectivity is the better choice.

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