Skip to main content
Glama
aldilaff
by aldilaff

wyze_set_light_effect

Set visual effects like color patterns or animations on Wyze light strips and compatible bulbs. Specify the device MAC and desired effect to customize lighting displays.

Instructions

Set visual effect for a Wyze light strip or compatible bulb

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_macYes
effectYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'wyze_set_light_effect' tool. It is decorated with @mcp.tool() which also serves as the registration. The function uses the Wyze SDK to set a light effect on the specified device by MAC address, checking device type compatibility and handling errors.
    @mcp.tool()
    def wyze_set_light_effect(device_mac: str, effect: str) -> Dict[str, str]:
        """Set visual effect for a Wyze light strip or compatible bulb"""
        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_effect(
                        device_mac=device_mac,
                        device_model=getattr(device, 'product_model', 'Unknown'),
                        effect=effect
                    )
                    return {"status": "success", "message": f"Set {device.nickname} effect to {effect}"}
            
            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 offers minimal behavioral insight. It implies a write/mutation operation ('Set') but doesn't disclose authentication needs, rate limits, side effects, or what happens if the device is offline. For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential information without unnecessary elaboration.

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 moderate complexity (mutation with 2 parameters) and the presence of an output schema (which handles return values), the description is minimally adequate but incomplete. It lacks parameter details, usage context, and behavioral transparency needed for safe operation. The output schema reduces but doesn't eliminate the need for more descriptive context.

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

Parameters2/5

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

Schema description coverage is 0%, so parameters are undocumented in the schema. The description mentions 'device_mac' and 'effect' implicitly but provides no details on format, allowed values, or examples. It doesn't compensate for the schema gap, leaving both parameters semantically unclear.

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 ('Set visual effect') and target resource ('for a Wyze light strip or compatible bulb'), making the purpose immediately understandable. It doesn't explicitly distinguish from siblings like wyze_set_color or wyze_set_color_temp, but the focus on 'visual effect' provides some differentiation. The description avoids tautology by not just restating the tool name.

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 like wyze_set_color or wyze_set_color_temp. It doesn't mention prerequisites (e.g., device must be on), compatibility limitations beyond 'light strip or compatible bulb', or error conditions. The agent must infer usage from context alone.

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