Skip to main content
Glama
Sign In
tuya-local-mcp

tuya-local-mcp

by meow-dot-py
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_lights

Retrieve Tuya and Smart Life light names, zones, targeting aliases, IP addresses, and preset names so you can identify and control specific local bulbs.

Instructions

List lights (name, zone, every word that targets them, IP) and preset names.

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": "list_lights"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/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 disclose the returned fields (including the useful hint that every targeting word/alias for a light is included), implying a safe read, but it never states that the call is side-effect free, what permissions are needed, or how presets are represented (names only).

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?

A single front-loaded sentence with a compact parenthetical listing the returned fields. Nothing is wasted or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter listing tool with no output schema, the description covers the key return fields, including the non-obvious alias words. It stops short of describing the shape (list vs map) or whether presets are returned flat or grouped, which is a minor gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The parenthetical instead usefully clarifies output content rather than input.

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?

States a specific verb and resource ("List lights") and enumerates the fields returned (name, zone, targeting words, IP) plus preset names. It does not distinguish itself from get_presets, which appears to serve the preset portion of the same request.

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?

There is no explicit when-to-use guidance and no mention of the obvious alternatives (light_status, get_presets). The agent must infer that this is a discovery/enumeration call, and the overlap with get_presets is left unresolved.

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

Deploy Server

Other Tools