Skip to main content
Glama
aldilaff
by aldilaff

wyze_set_color_temp

Adjust the color temperature of Wyze smart lights from warm (2700K) to cool (6500K) to match activities or preferences.

Instructions

Set color temperature for a Wyze light (2700K-6500K)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_macYes
color_tempYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function decorated with @mcp.tool(), implementing the logic to set color temperature on a Wyze light device. Validates input range, finds device by MAC, calls Wyze API, and returns status.
    @mcp.tool()
    def wyze_set_color_temp(device_mac: str, color_temp: int) -> Dict[str, str]:
        """Set color temperature for a Wyze light (2700K-6500K)"""
        try:
            if not 2700 <= color_temp <= 6500:
                return {"status": "error", "message": "Color temperature must be between 2700K and 6500K"}
            
            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_color_temp(
                        device_mac=device_mac,
                        device_model=getattr(device, 'product_model', 'Unknown'),
                        color_temp=color_temp
                    )
                    return {"status": "success", "message": f"Set {device.nickname} color temperature to {color_temp}K"}
            
            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 for behavioral disclosure. It implies a write operation ('Set') but doesn't mention permissions, side effects, error handling, or response format. The temperature range hint is useful, but critical behavioral details like whether this requires prior login or affects device state are missing.

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 directly states the tool's purpose and key constraint (temperature range). It's appropriately sized and front-loaded, 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 has an output schema (which handles return values) and only 2 parameters, the description is somewhat complete for a simple mutation tool. However, with no annotations and 0% schema coverage, it should do more to explain behavioral aspects like authentication needs or error cases, making it adequate but with clear gaps.

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 schema provides no parameter descriptions. The description adds value by clarifying that color_temp applies to a Wyze light and specifying the valid range (2700K-6500K), which helps interpret the integer parameter. However, it doesn't explain device_mac or provide format examples, leaving gaps.

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 color temperature') and target resource ('for a Wyze light'), with the specific temperature range (2700K-6500K) providing useful scope. However, it doesn't explicitly differentiate from sibling tools like wyze_set_brightness or wyze_set_color, which handle related but different light adjustments.

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_brightness, nor does it mention prerequisites such as device connectivity or authentication. It only states what the tool does, not when or why to choose it.

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