Skip to main content
Glama
aldilaff
by aldilaff

wyze_device_info

Retrieve detailed information about a specific Wyze smart home device using its MAC address to access device status and properties.

Instructions

Get detailed information about a specific Wyze device by MAC address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_macYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'wyze_device_info' tool. It uses the Wyze SDK to list devices and find the one matching the provided MAC address, returning detailed device information or an error if not found.
    @mcp.tool()
    def wyze_device_info(device_mac: str) -> Dict[str, Any]:
        """Get detailed information about a specific Wyze device by MAC address"""
        try:
            client = get_wyze_client()
            devices = client.devices_list()
            
            for device in devices:
                if device.mac == device_mac:
                    device_info = {
                        "mac": str(device.mac) if device.mac else "Unknown",
                        "nickname": str(device.nickname) if device.nickname else "Unknown",
                        "product_model": str(getattr(device, 'product_model', 'Unknown')) if getattr(device, 'product_model', 'Unknown') else "Unknown",
                        "product_type": str(getattr(device, 'product_type', 'Unknown')) if getattr(device, 'product_type', 'Unknown') else "Unknown",
                        "is_online": bool(getattr(device, 'is_online', True)),
                        "firmware_ver": str(getattr(device, 'firmware_ver', 'N/A')),
                        "device_model": str(getattr(device, 'device_model', 'Unknown')),
                    }
                    return {"status": "success", "device": device_info}
            
            return {"status": "error", "message": f"Device with MAC {device_mac} not found"}
        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 the full burden of behavioral disclosure. It states the tool retrieves 'detailed information' but doesn't specify what that includes (e.g., device type, settings, status), whether it's a read-only operation, authentication requirements, rate limits, or error handling. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded with the key action and resource, making it easy to parse. Every part of the sentence earns its place by specifying the action, target, and identifier.

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 (single parameter, no nested objects) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and incomplete behavioral details, it doesn't fully cover aspects like authentication needs or error cases. It meets basic requirements but lacks depth for a tool interacting with external devices.

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?

The description adds meaningful context for the single parameter 'device_mac' by specifying it's used to identify 'a specific Wyze device', which clarifies its purpose beyond the schema's basic title. With 0% schema description coverage and only one parameter, the description effectively compensates by explaining the parameter's role, though it doesn't detail format (e.g., MAC address structure) or examples.

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 action ('Get detailed information') and the target resource ('about a specific Wyze device by MAC address'). It distinguishes itself from sibling tools like 'wyze_get_devices' (which likely lists multiple devices) by specifying retrieval for a single device via MAC address. However, it doesn't explicitly contrast with other siblings like 'wyze_get_device_status', leaving some ambiguity about differentiation.

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 authentication via 'wyze_login'), exclusions, or comparisons to siblings like 'wyze_get_device_status' (which might provide different or overlapping information). Usage is implied only by the purpose, with no explicit context or alternatives stated.

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