mcp-tuya-close-door
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TUYA_HOST | Yes | The device's LAN IP or hostname; do not include protocol or port. | |
| TUYA_PORT | Yes | Device port, usually 6668, range 1–65535. | |
| TUYA_VERSION | Yes | Protocol version; only '3.4' is accepted. | |
| TUYA_CLOSE_DPS | No | Door-close DPS number; must be set together with TUYA_CLOSE_VALUE. | |
| TUYA_DEVICE_ID | Yes | Local Tuya device ID. | |
| TUYA_LOCAL_KEY | Yes | The device's 16-character Local Key. | |
| TUYA_CLOSE_VALUE | No | Corresponding door-close value as a JSON scalar (e.g., false, 1, or "close"). Must be set together with TUYA_CLOSE_DPS. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tuya_close_doorA | Send the configured local close command only after explicit confirmation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlapping purposes. The tool is trivially distinct and unambiguous.
The single tool follows a clear snake_case verb_noun convention with a vendor prefix (tuya_close_door), matching the server name. There are no competing conventions to create inconsistency.
One tool is exactly appropriate for a server whose stated purpose is a single specific action: closing a door via Tuya. The narrow scope justifies the minimal count, and the tool clearly earns its place.
For the declared domain of closing a door, the tool fully covers the action and even embeds the explicit confirmation requirement into its behavior. A status or dry-run tool would be a minor enhancement, not an obvious gap.