Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

networking_wake_on_lan

Read-onlyIdempotent

Construct Wake-on-LAN magic packets and cross-platform wake commands from a MAC address, with options to validate or analyze suitability. Results are computed locally without network transmission.

Instructions

Wake-on-LAN Magic Packet & Command Builder. Build a Wake-on-LAN (WOL) magic packet and ready-to-run wake commands for a target MAC address — it constructs the 102-byte packet hex and emits Linux/Windows/macOS/router/ Python/Node.js/Bash commands, but does not transmit anything itself (run the returned command to actually wake the host). Choose operation to scope the work: "generate" (all outputs), "packet" (packet bytes only), "commands" (per-platform commands), "validate" (check MAC/broadcast/port + setup tips), or "analyze" (MAC WOL-suitability). Computes locally from your input: no socket is opened, non-destructive, idempotent, and rate-limited (5 req/min anonymous, CAPTCHA above 15/hr).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
macYesTarget adapter MAC address; accepts colon, dash, dot, or bare 12-hex-digit formats.
operationNoWhich output to build: generate=all, packet=magic-packet bytes only, commands=per-platform wake commands, validate=setup check, analyze=MAC suitability.generate
broadcastNoBroadcast IPv4 address the wake commands target; ignored by the packet and analyze operations.255.255.255.255
portNoUDP port for the wake commands (7 Echo or 9 Discard are standard); used by commands, validate, and generate.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the build succeeded.
operationNoThe operation that was run, echoed back.
resultNoOperation-dependent payload. packet returns the magic-packet bytes (targetMAC, formattedMAC, packetHex, packetLength, synchronizationBytes, macRepetitions 16, totalSize 102, packetStructure). commands returns targetMAC, broadcastAddress, port, and per-platform commands. validate returns isValid, errors, warnings, setupTips, networkInfo. analyze returns mac, isUnicast, isLocallyAdministered, wolCompatible, notes, warnings. generate returns magicPacket, commands, validation, and macAnalysis combined.
errorNoFailure message (e.g. Invalid MAC address format); present only when success is false.
Behavior5/5

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

Discloses that computation is local, no socket opened, non-destructive, idempotent, rate-limited (5 req/min), and CAPTCHA required above 15/hr, adding context beyond the annotations that already declare readOnly, idempotent, and non-destructive.

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?

Description is informative and well-structured, with purpose first, then scope of operations, then behavioral notes. Slightly verbose but each sentence contributes necessary detail.

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 tool's complexity (multiple operations, rate limiting, local computation), the description covers all relevant aspects: functionality, limitations, behavior, and operational details. Output schema exists but description still adequately sets expectations.

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 covers 100% of parameters with descriptions and examples. Description adds value by explaining operation types and noting that broadcast and port are ignored for certain operations, enhancing understanding beyond schema constraints.

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?

Description clearly states the tool builds WOL magic packets and commands for a MAC address, lists five specific operations, and distinguishes from siblings by focusing on network wake functionality.

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?

Provides explicit guidance on when to use each operation ('Choose operation to scope the work'), clarifies that the tool does not transmit packets, and mentions rate limits, but does not explicitly list alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server