Packet Tracer Visual MCP

Overview Schema Source Related Servers Discussions Admin

ptv_probeServerServices

Scan Server-PT devices for DNS, HTTP, FTP, and DHCP service details without altering configurations. Identifies automation hints for network simulation tasks.

Instructions

Read-only probe for Server-PT service automation hints. It scans one Server-PT or all Server-PT devices for DNS/HTTP/FTP/DHCP related API names without changing services.

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_probeServerServices"
  }
}

Input Schema

Name	Required	Description	Default
`deviceName`	No
`maxDepth`	No
`maxKeys`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 18, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, description discloses key trait (read-only, no service changes). But lacks details on permissions, error handling, or response behavior.

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?

Single concise sentence, no redundancy. Could better structure to separate purpose from scope, but efficient.

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 3 parameters, no output schema, and no annotations, description is minimally adequate for a read-only probe but lacks parameter details and usage context among 22 sibling tools.

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 coverage is 0%, and description adds no explanation for deviceName, maxDepth, or maxKeys beyond their names. Meaningful parameter semantics absent.

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?

Explicitly states verb (probe/scan) and resource (Server-PT devices for DNS/HTTP/FTP/DHCP related API names). Distinguishes from sibling ptv_probeDeviceApi by specifying focus on service automation hints and read-only nature.

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 vs alternatives like ptv_probeDeviceApi. Only implies read-only probing without exclusions or prerequisites.

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