Skip to main content
Glama
aldilaff
by aldilaff

wyze_set_light_sun_match

Adjust Wyze light color temperature automatically based on time of day to match natural sunlight patterns for improved comfort and energy efficiency.

Instructions

Enable or disable sun matching for a Wyze light (adjusts color temperature based on time of day)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_macYes
enabledNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the wyze_set_light_sun_match tool. It uses the Wyze SDK to enable or disable sun matching (automatic color temperature adjustment based on time of day) for a specified light device by MAC address. The @mcp.tool() decorator registers this function as an MCP tool.
    @mcp.tool()
    def wyze_set_light_sun_match(device_mac: str, enabled: bool = True) -> Dict[str, str]:
        """Enable or disable sun matching for a Wyze light (adjusts color temperature based on time of day)"""
        try:
            client = get_wyze_client()
            devices = client.devices_list()
            
            for device in devices:
                if device.mac == device_mac and getattr(device, 'product_type', 'Unknown') in ['Light', 'Bulb', 'MeshLight', 'LightStrip']:
                    client.bulbs.set_sun_match(
                        device_mac=device_mac,
                        device_model=getattr(device, 'product_model', 'Unknown'),
                        sun_match=enabled
                    )
                    status = "enabled" if enabled else "disabled"
                    return {"status": "success", "message": f"Sun matching {status} for {device.nickname}"}
            
            return {"status": "error", "message": f"Light 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?

With no annotations provided, the description carries full burden but only states what the tool does functionally. It doesn't disclose behavioral traits like whether changes are immediate, if authentication is needed (implied by sibling wyze_login), error conditions, rate limits, or what the output contains. The description is minimal beyond the core function.

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 that front-loads the core action and explanation without any wasted words. Every part earns its place by specifying the tool's purpose and effect.

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 no annotations, 0% schema coverage, but an output schema exists, the description is minimally adequate. It covers the tool's function but lacks details on authentication, error handling, or output structure that would be helpful for a mutation tool in a device control context.

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?

Schema description coverage is 0%, so the description must compensate. It explains that 'enabled' toggles sun matching on/off, adding meaning beyond the schema's boolean type. However, it doesn't clarify 'device_mac' format or provide examples. With 0% coverage and 2 parameters, this is above baseline but not fully compensatory.

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 the specific action ('Enable or disable sun matching') on a specific resource ('Wyze light') with a functional explanation ('adjusts color temperature based on time of day'). It distinguishes from siblings like wyze_set_brightness or wyze_set_color_temp by focusing on automated time-based adjustments rather than manual settings.

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?

The description implies usage for automating light temperature based on time, but doesn't explicitly state when to use this versus alternatives like wyze_set_color_temp for manual control or wyze_set_light_effect for other effects. No guidance on prerequisites (e.g., device must be online) or exclusions is provided.

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