LG ThinQ

- PURPOSE: This is a read-only UI rendering tool that displays a confirmation dialog to the user before any control action is executed. It does NOT perform any device operation or state change. It simply presents action details in a visual card format and waits for the user's explicit approval or rejection. This tool must be used in UI-based clients to show a summary of the proposed action and collect user consent before any further step. Do not use this tool for read-only query commands such as history or analytics retrieval. - MANDATORY PREREQUISITE: You MUST call getAvailableProductsForControl IN THE SAME TURN, immediately BEFORE invoking this tool, EVERY time, to obtain the latest product list. NEVER reuse a product list from an earlier turn or skip this call — always re-fetch fresh data first, then invoke this tool immediately after it returns. - MANDATORY INVOCATION TIMING: This tool must be invoked only after the proposed action details have been successfully constructed using availableProduct information from a fresh getAvailableProductsForControl execution in the same turn. Never end the turn without invoking this tool when the user asked to control a device. - INPUT DATA: deviceAlias: Each argument in a single controlCommands array must contain only one independent capabilityCommand. String. User-friendly name of the product device. unit: String. Sub-unit of the product (e.g., fridge, freezer). capabilityId: String. The capability ID relevant to the action (e.g., temperatureControl). capabilityCommand: Object. Contains the parameters describing the proposed action. Please refer to the capabilitySchema for parameter names and formats.

askUserConfirmationBeforeControlForUI

- INTERNAL WIDGET TOOL — DO NOT CALL. This tool exists solely for the control/recommend/guide panel widgets to poll for pending card data. The assistant MUST NEVER invoke this tool.

fetchPendingWidgetUI

- PURPOSE: Fetch available product information to prepare a device CONTROL request. - ALWAYS FETCH FRESH: Invoke this command immediately before EVERY device control request to obtain the latest product list. NEVER reuse a product list from an earlier turn or an earlier tool result — always re-fetch fresh data. - CHAIN IN THE SAME TURN: Right after this command returns, continue IN THE SAME TURN and invoke askUserConfirmationBeforeControlForUI using the retrieved product list. Do NOT end the turn early — the confirmation card is rendered by the widget that this command already mounted.

getAvailableProductsForControl

- PURPOSE: Fetch available product information to prepare a read-only device QUERY or capability refresh. - ALWAYS FETCH FRESH: Invoke this command immediately before EVERY device query or capability refresh to obtain the latest product list. NEVER reuse a product list from an earlier turn or an earlier tool result — always re-fetch fresh data. - CHAIN IN THE SAME TURN: Right after this command returns, continue IN THE SAME TURN and invoke handleCommandForQuery, refreshSingleCapability, or refreshAllCapabilities using the retrieved product list.

getAvailableProductsForQuery

- PURPOSE: Fetch available product information to prepare contextual device RECOMMENDATIONS. - ALWAYS FETCH FRESH: Invoke this command immediately before EVERY recommendation request to obtain the latest product list. NEVER reuse a product list from an earlier turn or an earlier tool result — always re-fetch fresh data. - CHAIN IN THE SAME TURN: Right after this command returns, continue IN THE SAME TURN and invoke recommendDeviceFunctionForUI using the retrieved product list. Do NOT end the turn early — the recommendation card is rendered by the widget that this command already mounted.

getAvailableProductsForRecommend

- PURPOSE: Fetch available product information to prepare device USAGE GUIDES. - ALWAYS FETCH FRESH: Invoke this command immediately before EVERY usage guide request to obtain the latest product list. NEVER reuse a product list from an earlier turn or an earlier tool result — always re-fetch fresh data. - CHAIN IN THE SAME TURN: Right after this command returns, continue IN THE SAME TURN and invoke showDeviceUsageGuidesForUI using the retrieved product list. Do NOT end the turn early — the usage guide card is rendered by the widget that this command already mounted.

getAvailableProductsForUserGuide

- DEPRECATED — DO NOT CALL. This command is retained ONLY for backward compatibility with already-deployed clients. New requests MUST NOT invoke this command. - USE INSTEAD: Depending on the user's intent, call exactly ONE of the following purpose-specific commands, which secure the product list AND mount the correct widget for the follow-up user-facing tool: -- getAvailableProductsForControl for a device CONTROL request (followed by askUserConfirmationBeforeControlForUI) -- getAvailableProductsForRecommend for contextual RECOMMENDATIONS (followed by recommendDeviceFunctionForUI) -- getAvailableProductsForUserGuide for usage GUIDES (followed by showDeviceUsageGuidesForUI) -- getAvailableProductsForQuery for a read-only QUERY or capability refresh (followed by handleCommandForQuery, refreshSingleCapability, or refreshAllCapabilities)

getAvailableProductsNoUserFacingResponse

This tool is used by UI-based clients for backend execution of read-only queries. - MANDATORY PREREQUISITE: You MUST call getAvailableProductsForQuery IN THE SAME TURN, immediately BEFORE invoking this tool, EVERY time, to obtain the latest product list. NEVER reuse a product list from an earlier turn or skip this call — always re-fetch fresh data first.

handleCommandForQuery

This tool is used by UI-based clients for backend execution. For state-changing commands, do not invoke it directly in chat interfaces.

handleCommandFromUI

- PURPOSE: Display AI-generated device recommendations in a UI card format based on the user's situational context. This tool renders recommendations visually and does NOT execute any control commands. - MANDATORY INVOCATION: This tool MUST be invoked when the user's message implies a situational context that warrants device recommendations. Examples of trigger phrases: "I will come home at 10 PM", "It's hot", "I will sleep soon", "Leaving home", "Going to bed", "Working from home". In these situations, DO NOT present recommendations as plain text. Instead, you MUST call recommendDeviceFunctionForUI to display them via UI. - MANDATORY PREREQUISITE: You MUST call getAvailableProductsForRecommend IN THE SAME TURN, immediately BEFORE invoking this tool, EVERY time, to obtain the latest product list. NEVER reuse a product list from an earlier turn or skip this call — always re-fetch fresh data first. - REQUIRE PREPROCESSING: 1. Fetch a fresh product list via getAvailableProductsForRecommend as described above. 2. Infer suitable recommendations based on user context and available devices. 3. Construct aiRecommendations. 4. Invoke recommendDeviceFunctionForUI. - CRITICAL RULE: Recommendations MUST always be delivered using this tool, never as plain text. The user may then choose to act on a recommendation, at which point askUserConfirmationBeforeControlForUI should be used to perform the actual control. If the user context involves a schedule, recommendations must be related to the reservation function of the device.

recommendDeviceFunctionForUI