Skip to main content
Glama

connect_wireless

Attach a laptop or wireless client to a Wi-Fi network by SSID, security, and key, using DHCP or static IP, and report association and access point.

Instructions

Connect a laptop, PC or other client with a wireless card to a network: SSID, security and key, plus DHCP or a static address. Packet Tracer only associates when a network is loaded, so pktctl takes the network as bytes, sets the client's current profile, opens the result as a temporary copy (your own file is not written) and reports whether it associated and with which access point.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipNoStatic address. Omit for DHCP.
dnsNo
keyNo
maskNo
ssidYes
deviceYesClient with a wireless card, for example a laptop.
gatewayNo
securityNoopen
bring_access_pointNoMove the access point with this SSID next to the client first when it is out of radio range (Packet Tracer's radios reach about 120 units in the physical workspace).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipNoAddress of the wireless port; with DHCP, the lease if one arrived.
fileYesThe temporary copy Packet Tracer now has open. Your own file is untouched: save with `save_network` and a path to keep the change there.
ssidYes
deviceYes
diagnosisNoWhen the client did not associate: why, with the distance to each access point broadcasting the SSID.
associatedYes
access_pointNo
moved_access_pointNoThe access point that `bring_access_point` moved next to the client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.9/5.0
Behavior4/5

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

Adds real behavior beyond the annotations (readOnlyHint=false, destructiveHint=false): it sets the client's current profile, operates on a temporary copy so the user's own file is not written, and reports association status and the access point joined. That non-persistence guarantee and the returned outcome are exactly the kind of context annotations cannot carry.

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?

Two sentences, front-loaded with the purpose and then the notable behavior; almost every clause earns its place. Slightly dense but no filler.

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 need not be described, and annotations cover the safety profile. The description supplies the crucial non-persistence detail and the loaded-network prerequisite, leaving mainly the underserved ip/mask/gateway/dns parameters as a gap.

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 only 33% across 9 parameters, so the description must compensate. It covers ssid, security, key and the DHCP-vs-static distinction (ip 'Omit for DHCP'), but says nothing about mask, gateway, dns, or bring_access_point semantics. Partial compensation only.

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?

States a specific verb and resource ('Connect a laptop, PC or other client with a wireless card to a network') and enumerates the relevant inputs (SSID, security and key, DHCP or static address). The wireless-card scoping naturally separates it from the wired `connect` sibling.

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

Usage Guidelines3/5

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

Implies when it applies (a client with a wireless card, a loaded network) via the prerequisite 'Packet Tracer only associates when a network is loaded', but never names an alternative such as `connect`, `configure_host`, or `wireless_status`, nor states a when-not condition. Usage is inferable but not spelled out.

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