Skip to main content
Glama
aldilaff
by aldilaff

wyze_clear_light_timer

Clear scheduled timers for Wyze smart lights to stop automated on/off cycles. Specify the device MAC address to remove existing timer settings.

Instructions

Clear any scheduled timers for a Wyze light

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_macYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for wyze_clear_light_timer tool. Decorated with @mcp.tool() for automatic registration in FastMCP. Clears scheduled timers for the specified Wyze light device MAC address using wyze_sdk Client.bulbs.clear_timer.
    @mcp.tool()
    def wyze_clear_light_timer(device_mac: str) -> Dict[str, str]:
        """Clear any scheduled timers for a Wyze light"""
        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.clear_timer(
                        device_mac=device_mac,
                        device_model=getattr(device, 'product_model', 'Unknown')
                    )
                    return {"status": "success", "message": f"Cleared timer 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 the full burden of behavioral disclosure. It states the action ('Clear') but doesn't explain what 'clear' entails (e.g., permanent deletion, reversibility), required permissions, rate limits, or error conditions. This is a significant gap for a mutation tool with zero annotation coverage.

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 directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 reduces the need to describe return values) but no annotations and low parameter coverage, the description is minimally adequate. It covers the basic action but lacks details on behavior, usage context, and parameter meaning, making it incomplete for effective agent use.

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?

The description doesn't mention any parameters, and schema description coverage is 0%, leaving the single parameter 'device_mac' undocumented. Since there are no parameters described, the baseline is 4, but it's reduced to 3 because the description fails to add any meaning beyond the schema, such as explaining what 'device_mac' represents or its format.

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 ('Clear') and resource ('scheduled timers for a Wyze light'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'wyze_turn_off_device' or 'wyze_set_light_effect', which might also affect light behavior, so it falls short of a perfect score.

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, such as whether it should be used instead of adjusting brightness or turning off the device. It lacks context about prerequisites (e.g., needing timers set first) or exclusions, leaving usage unclear.

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