Skip to main content
Glama
Sign In
pt-mcp

pt-mcp

by kiskander
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Rename a Device

rename_device
Idempotent

Changes a Packet Tracer device's display name used by other tools without altering its IOS hostname; use CLI commands to change the hostname.

Instructions

Change a device's display name (the name used by all other tools). This does not change the IOS hostname; use send_cli_command with "hostname X" for that.

Examples:

  • "Rename Router0 to R1"

  • "Call PC0 'Accounting-PC'"

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": {
      "name": "<name>",
      "new_name": "<new_name>"
    },
    "name": "rename_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDevice display name as shown in Packet Tracer (e.g. 'Router0', 'PC1')
new_nameYesDevice 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

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation profile is known. The description adds important scope context that the display name is used by all other tools and that the IOS hostname is unaffected, though it does not discuss permissions or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core behavior and scope caveat, followed by two compact examples. Every sentence adds useful information with no repetition.

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

Completeness5/5

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

Given the annotations, full schema coverage, and an output schema, the description contains what an agent needs to invoke the tool correctly. The critical distinction between display name and hostname is covered explicitly.

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

Parameters4/5

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

Schema coverage is 100%, so a baseline of 3 is appropriate. The examples add useful meaning by showing that one argument is the current device name and the other is the new display name, especially since the schema descriptions for name and new_name are identical and do not distinguish them.

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 states a specific verb and resource: it changes a device's display name. It also distinguishes this from changing the IOS hostname, which prevents confusion with send_cli_command and other device-configuration siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the alternative for hostname changes: use send_cli_command with "hostname X". The examples further clarify the intended use with concrete rename requests.

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