tuya-local-mcp

Overview Schema Source Related Servers Discussions Admin

set_light

Control Tuya and Smart Life bulbs locally: set brightness, color, or color temperature, or apply scene presets to a room, zone, or single light, with an optional delay.

Instructions

Apply a preset/scene, or set brightness (1-100) with temp (0 warm-100 cool) OR rgb.

With a scene preset, target narrows it: target='bed', preset='focus' applies only focus's bed setting. Use either preset or manual values, not both.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_light"
  }
}

Input Schema

Name	Required	Default
`rgb`	No
`temp`	No
`preset`	No
`target`	No	all
`brightness`	No
`delay_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 6, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden. It does add useful behavior: value ranges (brightness 1-100, temp 0 warm to 100 cool), mode exclusivity, and target-narrowing semantics for presets. However it says nothing about delay_seconds (fade? schedule?), error behavior for invalid values, or whether the light must be powered on first.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then the preset/target nuance, then the exclusivity constraint. Three tight sentences with no filler; only the unqualified 'rgb' leaves an avoidable ambiguity.

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?

For a 6-parameter mutation tool with no annotations, no output schema, and zero schema descriptions, the definition covers the primary path well but leaves delay_seconds, rgb encoding, and result/permission behavior undocumented.

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 description must compensate. It documents ranges and meaning for brightness, temp, rgb (conceptually), preset, and target, but delay_seconds is entirely undefined and the rgb format (length, 0-255 range?) is not specified.

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?

States specific verbs and resources: applying a preset/scene vs. setting brightness with temp or rgb. An agent can tell this apart from power_light (on/off) and light_status without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the mutual-exclusion rule ('use either preset or manual values, not both') and explains how target interacts with preset. It does not say when to choose this over power_light (e.g., whether the light must already be on), which keeps it short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server