alexa_lock
Lock or unlock a connected smart door lock via Alexa, with user confirmation required before unlocking to protect home security.
Instructions
Lock or unlock a smart lock (door lock) connected to Alexa. Unlocking reduces your home’s security, so confirm the user really wants it unlocked. Amazon may require a voice PIN or the Alexa app to unlock; its refusal is reported as an error. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"target": "<target>",
"action": "<action>"
},
"name": "alexa_lock"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | lock or unlock. | |
| target | Yes | Lock name (or id) from alexa_list_smart_home. | |
| confirmToken | No | ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation. |