Skip to main content
Glama

network_search

Read-onlyIdempotent

Search observed WiFi networks by SSID, BSSID, location, or encryption to retrieve network details from a global wardriving database.

Instructions

Search WiGLE's database of observed WiFi networks by SSID, BSSID, location, or encryption.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity name
ssidNoExact SSID to match
bssidNoMAC address / BSSID to match, e.g. 'AA:BB:CC:DD:EE:FF'
regionNoState/region name
countryNoTwo-letter country code, e.g. 'US'
lat_maxNoMaximum latitude of bounding box
lat_minNoMinimum latitude of bounding box
long_maxNoMaximum longitude of bounding box
long_minNoMinimum longitude of bounding box
only_openNoIf true, only return networks with no encryption
ssid_likeNoSQL LIKE pattern for SSID, e.g. 'Pretty Fly%'
encryptionNoEncryption filter, e.g. 'wpa', 'wpa2', 'wep', 'none'
search_afterNoPagination cursor from a previous response's 'search_after' field
results_per_pageNoMax results to return (1-100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, establishing safety and idempotency. The description adds 'Search WiGLE's database', reinforcing a read-only operation. No contradictions, and the description provides minimal but sufficient behavioral context on top of annotations.

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?

A single sentence that front-loads the main action and scope. No redundant words or unnecessary details. Every part of the description earns its place.

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?

Given the tool has 14 optional parameters and an output schema exists, the description adequately covers the tool's purpose. It does not explain pagination or the 'search_after' parameter, but these are documented in the schema. The description is complete enough for an agent to understand core functionality.

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%, so each parameter is already documented. The tool description summarizes the parameter categories (SSID, BSSID, location, encryption) but adds no new semantic detail beyond what the schema provides. Baseline score of 3 is appropriate.

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 clearly states it searches WiGLE's database of WiFi networks by multiple criteria (SSID, BSSID, location, or encryption). The tool name 'network_search' and the description distinguish it from sibling tools like 'bluetooth_search' and 'network_detail', which focus on different network types or individual records.

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?

No explicit guidance on when to use this tool versus alternatives. While the name and description imply WiFi network search, and siblings suggest alternatives for other network types, the description does not state when to prefer this over more specific tools like 'network_detail' or when to use pagination parameters.

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/thehappydinoa/wigle-mcp'

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