Packet Tracer Visual MCP

Overview Schema Source Related Servers Discussions Admin

ptv_configurePc

Configure a PC or Server network settings including IPv4 address, subnet mask, gateway, DNS, or enable DHCP in Packet Tracer simulations.

Instructions

Set a PC or Server IPv4 address, mask, gateway, DNS, or DHCP flag.

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": {
      "deviceName": "<deviceName>"
    },
    "name": "ptv_configurePc"
  }
}

Input Schema

Name	Required	Description	Default
`deviceName`	Yes
`dhcp`	No
`ip`	No
`mask`	No
`gateway`	No
`dns`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 18, 2026

TDQS

C2.9/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 carry the burden. It only states 'Set' implying mutation, but does not disclose behavioral traits like idempotency, error states, or consequences of setting DHCP alongside IP fields.

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 description is highly concise with one sentence and no unnecessary words. However, the brevity borders on under-specification, sacrificing some informational value.

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

Completeness2/5

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

Given the tool has 6 parameters, no output schema, and no annotations, the description is incomplete. It fails to specify required parameters, behavior when DHCP is true, return values, or error conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description merely lists the parameter names without adding format constraints, relationships (e.g., DHCP vs IP), or default behavior. It does not compensate for the schema's lack of clarity.

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 uses the specific verb 'Set' and clearly identifies the resource as 'PC or Server IPv4 address, mask, gateway, DNS, or DHCP flag'. It distinguishes from siblings like ptv_configureIos (for IOS devices) and ptv_addDevice (adding devices).

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 such as ptv_configureIos. There is no discussion of prerequisites, context, or exclusions.

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