Skip to main content
Glama
apiarya

WeMo MCP Server

by apiarya
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

scan_network

Discover WeMo smart home devices on your local network by scanning a specified subnet. Probes common ports and verifies responsive IPs to identify and list all WeMo devices with full details.

Instructions

Scan network for WeMo devices using pywemo discovery.

This tool scans the specified subnet for WeMo devices by:

  1. Probing all IPs in the subnet on common WeMo ports (49152-49155)

  2. Verifying responsive IPs by attempting to read device descriptions

  3. Using pywemo library to properly identify and parse WeMo devices

Args:

subnet: Network subnet in CIDR notation (default: from config or "192.168.1.0/24")
timeout: Connection timeout in seconds for port probing (default: from config or 0.6)
max_workers: Maximum concurrent workers for network scanning (default: from config or 60)
ctx: MCP context injected by FastMCP; used to elicit the subnet when none is configured

Returns:

Dictionary containing:
- scan_parameters: The parameters used for scanning
- results: Summary with device counts
- devices: List of discovered WeMo devices with full details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subnetNo
timeoutNo
max_workersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

Describes the scanning steps: probing ports, verifying responsiveness, using pywemo. However, it omits potential side effects like network load or that scanning may be slow.

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?

Well-organized with clear sections (purpose, steps, args, returns). Could be slightly more concise but appropriate for the complexity.

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?

Covers input, process, and output adequately. No annotations or schema descriptions, but description provides thorough details. Missing error handling or empty results clarification.

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

Parameters5/5

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

With 0% schema coverage, the description fully compensates by explaining all three parameters including defaults and context usage. Each parameter is described with sufficient detail.

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?

Clearly states the tool scans network for WeMo devices using pywemo. Verb 'scan' and resource 'network for WeMo devices' are specific and distinguish from siblings like list_devices or control_device.

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?

Implied usage for initial device discovery but no explicit when-to-use or when-not-to-use compared to sibling tools. The description lacks guidance on 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/apiarya/wemo-mcp-server'

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