Skip to main content
Glama
aldilaff
by aldilaff

wyze_get_device_status

Retrieve current status information for Wyze smart home devices, including power state and brightness levels, to monitor device conditions.

Instructions

Get accurate current status for a Wyze device (power state, brightness, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_macYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'wyze_get_device_status' tool, decorated with @mcp.tool() for automatic registration. It retrieves the current status of a Wyze device by MAC address, providing detailed information like power state, brightness, color temperature, and color for light devices, or online status for others.
    @mcp.tool()
    def wyze_get_device_status(device_mac: str) -> Dict[str, Any]:
        """Get accurate current status for a Wyze device (power state, brightness, etc.)"""
        try:
            client = get_wyze_client()
            devices = client.devices_list()
            
            # Find the device first
            target_device = None
            for device in devices:
                if device.mac == device_mac:
                    target_device = device
                    break
            
            if not target_device:
                return {"status": "error", "message": f"Device with MAC {device_mac} not found"}
            
            device_type = getattr(target_device, 'product_type', 'Unknown')
            device_status = {
                "mac": device_mac,
                "nickname": target_device.nickname,
                "product_type": device_type,
                "product_model": getattr(target_device, 'product_model', 'Unknown'),
            }
            
            # Get detailed status based on device type
            if device_type in ['Light', 'Bulb', 'MeshLight', 'LightStrip']:
                try:
                    detailed_device = client.bulbs.info(device_mac=device_mac)
                    if detailed_device:
                        device_status.update({
                            "is_on": getattr(detailed_device, 'is_on', None),
                            "brightness": getattr(detailed_device, 'brightness', None),
                            "color_temp": getattr(detailed_device, 'color_temp', None),
                            "color": getattr(detailed_device, 'color', None),
                        })
                    else:
                        device_status["error"] = "Could not retrieve detailed bulb information"
                except Exception as e:
                    device_status["error"] = f"Error getting bulb status: {str(e)}"
                    
            else:
                # For other device types, show basic online status
                device_status["is_online"] = getattr(target_device, 'is_online', None)
            
            return {"status": "success", "device_status": device_status}
            
        except WyzeClientConfigurationError as e:
            return {"status": "error", "message": f"Configuration error: {str(e)}"}
        except WyzeRequestError as e:
            return {"status": "error", "message": f"API error: {str(e)}"}
        except Exception as e:
            return {"status": "error", "message": f"Unexpected error: {str(e)}"}
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read-only operation ('Get') but doesn't disclose behavioral traits such as authentication needs, rate limits, error conditions, or what 'accurate current status' entails (e.g., real-time vs. cached). The description is minimal and lacks crucial operational context.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core purpose and includes helpful examples ('power state, brightness, etc.') without unnecessary elaboration, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (1 parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and 0% schema coverage, it lacks details on authentication, error handling, and parameter semantics, leaving gaps in operational context.

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 0%, so the description must compensate. It doesn't mention the device_mac parameter at all, nor does it explain its format or sourcing. However, with only 1 parameter and an output schema present, the baseline is slightly higher, but the description adds no value beyond the schema's structural definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('current status for a Wyze device'), including examples of what status means ('power state, brightness, etc.'). It distinguishes from siblings like wyze_get_devices (which likely lists devices) and wyze_device_info (which might provide static metadata), but doesn't explicitly name these alternatives.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing device_mac), exclusions, or compare it to siblings like wyze_device_info or wyze_get_devices, leaving the agent to infer usage context.

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/aldilaff/mcp-wyze-server'

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