Skip to main content
Glama
Sign In
WiFi Scanner MCP

WiFi Scanner MCP

by Swedishwizards
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Scan nearby Wi-Fi networks

scan_wifi_networks
Read-onlyIdempotent

Scans nearby Wi-Fi networks and lists SSID, signal strength, channel, band, security type, and connection status to help identify available networks or check which one is connected.

Instructions

Scan for Wi-Fi networks near this computer and list them with name (SSID), signal strength (dBm, %, quality and 1-4 bars), channel, band (2.4/5/6 GHz), security type (open/WEP/WPA/WPA2/WPA3/enterprise) and whether this computer is connected to it. Use it when the user asks which Wi-Fi networks are around, which one is strongest, or to find a specific network. Read-only; does not connect to anything.

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": "scan_wifi_networks"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNoOnly return networks on this band (default "all").
freshNoForce a new scan instead of reusing one from the last 15 seconds.
limitNoMaximum number of networks to return (default 100).
sort_byNoSort order (default "signal", connected network first).
include_hiddenNoInclude networks that hide their name (default false).
min_signal_dbmNoOnly return networks at least this strong, e.g. -70.
group_by_networkNoMerge access points that share a network name into one entry (default true). Set false to list every access point / BSSID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds specific value by clarifying that the scan "does not connect to anything" and by documenting the return payload shape, which matters because there is no output schema.

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?

Three sentences, each doing distinct work: capability plus return fields, then usage triggers, then a safety note. The long field enumeration is front-loaded and justified because no output schema exists to carry that information.

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?

For a seven-parameter, fully-optional scan tool with complete schema coverage and no output schema, the description covers purpose, inputs by implication, usage triggers, safety, and result shape. Nothing an agent needs before calling it is missing.

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 description coverage is 100%, with all seven optional parameters (band, fresh, limit, sort_by, include_hidden, min_signal_dbm, group_by_network) documented including defaults and enums. The description adds no parameter-specific meaning beyond the schema, so the baseline 3 applies.

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 ("Scan for Wi-Fi networks near this computer and list them") and enumerates exactly what each entry contains (SSID, dBm/%/bars, channel, band, security, connected flag). This is far more specific than the sibling names alone would suggest and lets an agent distinguish a raw scan from channel analysis or current-connection lookup.

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?

Explicitly names three triggering user intents: which networks are around, which is strongest, and finding a specific network. It does not exclude the sibling tools (get_current_wifi, analyze_wifi_channels) or say when analyzing channels would be the better choice, so the routing guidance stops one step short of a 5.

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