coffeemaker_getAvailableBeverages
ChatGPTGet the available beverages of the coffee maker. Returns an object with the available beverages with their internal identifiers for starting a brew and translated human-readable names for display. Use this tool to see what beverages exist before starting a brew. IMPORTANT: When starting a brew, you have to map the translated name used by the human to the corresponding internal identifier. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. Output Schema The tool returns json data with the following structure: - beverages (array<object>): Array of beverages the coffee maker can prepare. - beverage (enum): Internal key of the beverage. Use as input when starting a brew. Do not display to the user. - translation (string): Human-readable name of the beverage in the requested language for display purposes. Display to the user as-is. - description (string): Short description of the beverage explaining characteristics.
coffeemaker_getAvailableBeverages
ChatGPTGet the available beverages of the coffee maker. Returns an object with the available beverages with their internal identifiers for starting a brew and translated human-readable names for display. Use this tool to see what beverages exist before starting a brew. IMPORTANT: When starting a brew, you have to map the translated name used by the human to the corresponding internal identifier. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. Output Schema The tool returns json data with the following structure: - beverages (array<object>): Array of beverages the coffee maker can prepare. - beverage (enum): Internal key of the beverage. Use as input when starting a brew. Do not display to the user. - translation (string): Human-readable name of the beverage in the requested language for display purposes. Display to the user as-is. - description (string): Short description of the beverage explaining characteristics.
coffeemaker_getAvailableBeverages
ChatGPTGet the available beverages of the coffee maker. Returns an object with the available beverages with their internal identifiers for starting a brew and translated human-readable names for display. Use this tool to see what beverages exist before starting a brew. IMPORTANT: When starting a brew, you have to map the translated name used by the human to the corresponding internal identifier. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. Output Schema The tool returns json data with the following structure: - beverages (array<object>): Array of beverages the coffee maker can prepare. - beverage (enum): Internal key of the beverage. Use as input when starting a brew. Do not display to the user. - translation (string): Human-readable name of the beverage in the requested language for display purposes. Display to the user as-is. - description (string): Short description of the beverage explaining characteristics.
coffeemaker_getAvailableFavoriteBeverages
ChatGPTGet the user's saved favorite beverages for coffee makers. These are pre-configured beverage recipes with pre-configured settings that the user has saved for quick access. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of a specific coffee maker. If no haId is provided, the tool returns the favorites for all coffee makers. Use haId as obtained from getAvailableAppliances. Output Schema The tool returns json data with the following structure: - favorites (array<object>): Array of the user's saved favorites of the user's supported appliances with pre-configured settings - haId (string): Home Connect appliance ID for which the favorite is defined. Used internally when starting the favorite, do not show to the user. - applianceName (string): The user-assigned name of the coffee maker this favorite belongs to. Display this to help users identify which appliance the favorite is for. - favoriteId (string): Unique identifier for this favorite (used internally, never show this to the user) - beverage (string): Name of the beverage type this favorite brews. - description (string): Generic description of the beverage type that the favorite brews. Misses specific settings of the favorite specified via the options. Use this as context to select the appropriate favorite. - options (array<string>): List of option key-value pairs that define the specific settings of this favorite. Use to show the user what makes this favorite special. - favoriteName (string): Human-readable name of this favorite displayed to users
coffeemaker_getAvailableFavoriteBeverages
ChatGPTGet the user's saved favorite beverages for coffee makers. These are pre-configured beverage recipes with pre-configured settings that the user has saved for quick access. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of a specific coffee maker. If no haId is provided, the tool returns the favorites for all coffee makers. Use haId as obtained from getAvailableAppliances. Output Schema The tool returns json data with the following structure: - favorites (array<object>): Array of the user's saved favorites of the user's supported appliances with pre-configured settings - haId (string): Home Connect appliance ID for which the favorite is defined. Used internally when starting the favorite, do not show to the user. - applianceName (string): The user-assigned name of the coffee maker this favorite belongs to. Display this to help users identify which appliance the favorite is for. - favoriteId (string): Unique identifier for this favorite (used internally, never show this to the user) - beverage (string): Name of the beverage type this favorite brews. - description (string): Generic description of the beverage type that the favorite brews. Misses specific settings of the favorite specified via the options. Use this as context to select the appropriate favorite. - options (array<string>): List of option key-value pairs that define the specific settings of this favorite. Use to show the user what makes this favorite special. - favoriteName (string): Human-readable name of this favorite displayed to users
coffeemaker_getAvailableFavoriteBeverages
ChatGPTGet the user's saved favorite beverages for coffee makers. These are pre-configured beverage recipes with pre-configured settings that the user has saved for quick access. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of a specific coffee maker. If no haId is provided, the tool returns the favorites for all coffee makers. Use haId as obtained from getAvailableAppliances. Output Schema The tool returns json data with the following structure: - favorites (array<object>): Array of the user's saved favorites of the user's supported appliances with pre-configured settings - haId (string): Home Connect appliance ID for which the favorite is defined. Used internally when starting the favorite, do not show to the user. - applianceName (string): The user-assigned name of the coffee maker this favorite belongs to. Display this to help users identify which appliance the favorite is for. - favoriteId (string): Unique identifier for this favorite (used internally, never show this to the user) - beverage (string): Name of the beverage type this favorite brews. - description (string): Generic description of the beverage type that the favorite brews. Misses specific settings of the favorite specified via the options. Use this as context to select the appropriate favorite. - options (array<string>): List of option key-value pairs that define the specific settings of this favorite. Use to show the user what makes this favorite special. - favoriteName (string): Human-readable name of this favorite displayed to users
coffeemaker_getStatus
ChatGPTGet the current status of: the coffee maker e.g. power state; active brewing beverage; and operation state e.g. rinsing/running/finished. Use this tool to check what the coffee maker is currently doing. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Note: Program names and settings in the response are already localized and should be preserved as-is when translating other parts of the response to the user's language. Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances.
coffeemaker_getStatus
ChatGPTGet the current status of: the coffee maker e.g. power state; active brewing beverage; and operation state e.g. rinsing/running/finished. Use this tool to check what the coffee maker is currently doing. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Note: Program names and settings in the response are already localized and should be preserved as-is when translating other parts of the response to the user's language. Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances.
coffeemaker_getStatus
ChatGPTGet the current status of: the coffee maker e.g. power state; active brewing beverage; and operation state e.g. rinsing/running/finished. Use this tool to check what the coffee maker is currently doing. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Note: Program names and settings in the response are already localized and should be preserved as-is when translating other parts of the response to the user's language. Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances.
coffeemaker_powerOff
ChatGPTSwitch the coffee maker main power to OFF to stop the appliance. - Does NOT stop or interrupt an active brew. Instead it will fail if still actively brewing. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. Handling User Action Requests Some tool responses may ask the user to perform a physical action that must be performed on the appliance directly and confirmed (e.g., "Is the milk container empty?"). The tool response "Please enable remote start first." is an example of such a request. In this case, please ask the user to enable remote start on their appliance and/or in the Home Connect app, and then confirm with you once done. IMPORTANT: These confirmation requests cannot be automatically fulfilled via a tool call. They must be confirmed on the appliance directly. When you encounter such responses: 1. Parse the request: Extract what action the user needs to perform (e.g., "connect the milk container", "close the door") 2. Inform the user: Clearly explain what they need to do physically with their appliance 3. Wait for confirmation: Ask the user to confirm the action once they've completed the action and if you should retry the operation 4. Retry the operation: Only if the user confirms they performed the action and asks you to retry, retry the same tool call - the issue should be resolved If the same error or request persists when retrying after user confirmation, inform the user and suggest they check the appliance manually. Never automatically/implicitly "confirm" actions that require physical user intervention - always wait for actual user confirmation! Example Flow - Tool returns: "Is the milk container empty?" - Your response: "Please empty the milk container and confirm it on the appliance directly. This cannot be done remotely. Once done, I can try powering off again." - User confirms: "Done" or "Ok" - Your action: Ask if you should retry the previous operation
coffeemaker_powerOff
ChatGPTSwitch the coffee maker main power to OFF to stop the appliance. - Does NOT stop or interrupt an active brew. Instead it will fail if still actively brewing. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. Handling User Action Requests Some tool responses may ask the user to perform a physical action that must be performed on the appliance directly and confirmed (e.g., "Is the milk container empty?"). The tool response "Please enable remote start first." is an example of such a request. In this case, please ask the user to enable remote start on their appliance and/or in the Home Connect app, and then confirm with you once done. IMPORTANT: These confirmation requests cannot be automatically fulfilled via a tool call. They must be confirmed on the appliance directly. When you encounter such responses: 1. Parse the request: Extract what action the user needs to perform (e.g., "connect the milk container", "close the door") 2. Inform the user: Clearly explain what they need to do physically with their appliance 3. Wait for confirmation: Ask the user to confirm the action once they've completed the action and if you should retry the operation 4. Retry the operation: Only if the user confirms they performed the action and asks you to retry, retry the same tool call - the issue should be resolved If the same error or request persists when retrying after user confirmation, inform the user and suggest they check the appliance manually. Never automatically/implicitly "confirm" actions that require physical user intervention - always wait for actual user confirmation! Example Flow - Tool returns: "Is the milk container empty?" - Your response: "Please empty the milk container and confirm it on the appliance directly. This cannot be done remotely. Once done, I can try powering off again." - User confirms: "Done" or "Ok" - Your action: Ask if you should retry the previous operation
coffeemaker_powerOff
ChatGPTSwitch the coffee maker main power to OFF to stop the appliance. - Does NOT stop or interrupt an active brew. Instead it will fail if still actively brewing. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. Handling User Action Requests Some tool responses may ask the user to perform a physical action that must be performed on the appliance directly and confirmed (e.g., "Is the milk container empty?"). The tool response "Please enable remote start first." is an example of such a request. In this case, please ask the user to enable remote start on their appliance and/or in the Home Connect app, and then confirm with you once done. IMPORTANT: These confirmation requests cannot be automatically fulfilled via a tool call. They must be confirmed on the appliance directly. When you encounter such responses: 1. Parse the request: Extract what action the user needs to perform (e.g., "connect the milk container", "close the door") 2. Inform the user: Clearly explain what they need to do physically with their appliance 3. Wait for confirmation: Ask the user to confirm the action once they've completed the action and if you should retry the operation 4. Retry the operation: Only if the user confirms they performed the action and asks you to retry, retry the same tool call - the issue should be resolved If the same error or request persists when retrying after user confirmation, inform the user and suggest they check the appliance manually. Never automatically/implicitly "confirm" actions that require physical user intervention - always wait for actual user confirmation! Example Flow - Tool returns: "Is the milk container empty?" - Your response: "Please empty the milk container and confirm it on the appliance directly. This cannot be done remotely. Once done, I can try powering off again." - User confirms: "Done" or "Ok" - Your action: Ask if you should retry the previous operation
coffeemaker_powerOn
ChatGPTSwitch the coffee maker main power to ON to start the appliance. - The appliance may take a moment to be ready to accept commands. - Does NOT start brewing; use the coffeemaker_startBrewing tool to begin a brew. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. Handling User Action Requests Some tool responses may ask the user to perform a physical action that must be performed on the appliance directly and confirmed (e.g., "Please enable remote start first."). The tool response "Please enable remote start first." is an example of such a request. In this case, please ask the user to enable remote start on their appliance and/or in the Home Connect app, and then confirm with you once done. IMPORTANT: These confirmation requests cannot be automatically fulfilled via a tool call. They must be confirmed on the appliance directly. When you encounter such responses: 1. Parse the request: Extract what action the user needs to perform (e.g., "connect the milk container", "close the door") 2. Inform the user: Clearly explain what they need to do physically with their appliance 3. Wait for confirmation: Ask the user to confirm the action once they've completed the action and if you should retry the operation 4. Retry the operation: Only if the user confirms they performed the action and asks you to retry, retry the same tool call - the issue should be resolved If the same error or request persists when retrying after user confirmation, inform the user and suggest they check the appliance manually. Never automatically/implicitly "confirm" actions that require physical user intervention - always wait for actual user confirmation! Example Flow - Tool returns: "Please enable remote start first." - Your response: "I need you to enable remote start on your coffee maker. Once you've done that, let me know and I'll try powering it on again." - User confirms: "Done" or "Ok" - Your action: Ask if you should retry the previous operation
coffeemaker_powerOn
ChatGPTSwitch the coffee maker main power to ON to start the appliance. - The appliance may take a moment to be ready to accept commands. - Does NOT start brewing; use the coffeemaker_startBrewing tool to begin a brew. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. Handling User Action Requests Some tool responses may ask the user to perform a physical action that must be performed on the appliance directly and confirmed (e.g., "Please enable remote start first."). The tool response "Please enable remote start first." is an example of such a request. In this case, please ask the user to enable remote start on their appliance and/or in the Home Connect app, and then confirm with you once done. IMPORTANT: These confirmation requests cannot be automatically fulfilled via a tool call. They must be confirmed on the appliance directly. When you encounter such responses: 1. Parse the request: Extract what action the user needs to perform (e.g., "connect the milk container", "close the door") 2. Inform the user: Clearly explain what they need to do physically with their appliance 3. Wait for confirmation: Ask the user to confirm the action once they've completed the action and if you should retry the operation 4. Retry the operation: Only if the user confirms they performed the action and asks you to retry, retry the same tool call - the issue should be resolved If the same error or request persists when retrying after user confirmation, inform the user and suggest they check the appliance manually. Never automatically/implicitly "confirm" actions that require physical user intervention - always wait for actual user confirmation! Example Flow - Tool returns: "Please enable remote start first." - Your response: "I need you to enable remote start on your coffee maker. Once you've done that, let me know and I'll try powering it on again." - User confirms: "Done" or "Ok" - Your action: Ask if you should retry the previous operation
coffeemaker_powerOn
ChatGPTSwitch the coffee maker main power to ON to start the appliance. - The appliance may take a moment to be ready to accept commands. - Does NOT start brewing; use the coffeemaker_startBrewing tool to begin a brew. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. Handling User Action Requests Some tool responses may ask the user to perform a physical action that must be performed on the appliance directly and confirmed (e.g., "Please enable remote start first."). The tool response "Please enable remote start first." is an example of such a request. In this case, please ask the user to enable remote start on their appliance and/or in the Home Connect app, and then confirm with you once done. IMPORTANT: These confirmation requests cannot be automatically fulfilled via a tool call. They must be confirmed on the appliance directly. When you encounter such responses: 1. Parse the request: Extract what action the user needs to perform (e.g., "connect the milk container", "close the door") 2. Inform the user: Clearly explain what they need to do physically with their appliance 3. Wait for confirmation: Ask the user to confirm the action once they've completed the action and if you should retry the operation 4. Retry the operation: Only if the user confirms they performed the action and asks you to retry, retry the same tool call - the issue should be resolved If the same error or request persists when retrying after user confirmation, inform the user and suggest they check the appliance manually. Never automatically/implicitly "confirm" actions that require physical user intervention - always wait for actual user confirmation! Example Flow - Tool returns: "Please enable remote start first." - Your response: "I need you to enable remote start on your coffee maker. Once you've done that, let me know and I'll try powering it on again." - User confirms: "Done" or "Ok" - Your action: Ask if you should retry the previous operation
coffeemaker_startBrewing
ChatGPTStart brewing a selected type of beverage such as coffee, espresso, or hot water. - The coffee maker needs to be powered on and ready. - Only the beverages returned by coffeemaker_getAvailableBeverages are supported, otherwise the tool will fail. - If the user's request does not exactly match a supported beverage, ask for clarification rather than guessing. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Required: beverage (enum): The desired type of beverage as returned by coffeemaker_getAvailableBeverages. - Optional: size (enum): The beverage size between Small and ExtraLarge. The size is relative depending on the beverage. A volume in ml is not supported. - Optional: strength (enum): The coffee strength. The supported values depend on the beverage type. - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. CRITICAL SAFETY REQUIREMENT - Multiple Beverage Handling: Coffee makers can brew exactly one (1) beverage at a time. When a user requests multiple beverages: 1. Brew the first beverage using this tool 2. STOP and wait - Do NOT call this tool again 3. Explicitly tell the user: "I've started brewing [beverage]. Please remove the cup when it's done and place a new cup, then let me know when you're ready for the next beverage." 4. Only proceed after the user explicitly confirms the cup has been replaced The same applies for rinse cycles: Always wait for user confirmation that a cup is in place after a rinse operation took place. Hard constraints: - This tool MUST NOT be called more than once in a single assistant response - Never assume the cup has been replaced - Never call this tool to brew again without explicit user confirmation Violating these rules will cause spills and overflow. Important: If the brew cannot be started because the coffee machine needs to be cleaned, the user must be instructed to perform the required action on the appliance directly before retrying. This cannot be done remotely. See the example below for how to handle such cases. Handling User Action Requests Some tool responses may ask the user to perform a physical action that must be performed on the appliance directly and confirmed (e.g., "The coffee machine needs to (be cleaned|run the cleaning program|be descaled|run the Calc'n'Clean program). Please say [OK] if you'd like to continue with the selected program anyway.", "Please make sure no one is currently using your coffee machine and say [OK].", "Is the milk still fresh?", "Please close the door and say [OK]."). The tool response "Please enable remote start first." is an example of such a request. In this case, please ask the user to enable remote start on their appliance and/or in the Home Connect app, and then confirm with you once done. IMPORTANT: These confirmation requests cannot be automatically fulfilled via a tool call. They must be confirmed on the appliance directly. When you encounter such responses: 1. Parse the request: Extract what action the user needs to perform (e.g., "connect the milk container", "close the door") 2. Inform the user: Clearly explain what they need to do physically with their appliance 3. Wait for confirmation: Ask the user to confirm the action once they've completed the action and if you should retry the operation 4. Retry the operation: Only if the user confirms they performed the action and asks you to retry, retry the same tool call - the issue should be resolved If the same error or request persists when retryin…
coffeemaker_startBrewing
ChatGPTStart brewing a selected type of beverage such as coffee, espresso, or hot water. - The coffee maker needs to be powered on and ready. - Only the beverages returned by coffeemaker_getAvailableBeverages are supported, otherwise the tool will fail. - If the user's request does not exactly match a supported beverage, ask for clarification rather than guessing. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Required: beverage (enum): The desired type of beverage as returned by coffeemaker_getAvailableBeverages. - Optional: size (enum): The beverage size between Small and ExtraLarge. The size is relative depending on the beverage. A volume in ml is not supported. - Optional: strength (enum): The coffee strength. The supported values depend on the beverage type. - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. CRITICAL SAFETY REQUIREMENT - Multiple Beverage Handling: Coffee makers can brew exactly one (1) beverage at a time. When a user requests multiple beverages: 1. Brew the first beverage using this tool 2. STOP and wait - Do NOT call this tool again 3. Explicitly tell the user: "I've started brewing [beverage]. Please remove the cup when it's done and place a new cup, then let me know when you're ready for the next beverage." 4. Only proceed after the user explicitly confirms the cup has been replaced The same applies for rinse cycles: Always wait for user confirmation that a cup is in place after a rinse operation took place. Hard constraints: - This tool MUST NOT be called more than once in a single assistant response - Never assume the cup has been replaced - Never call this tool to brew again without explicit user confirmation Violating these rules will cause spills and overflow. Important: If the brew cannot be started because the coffee machine needs to be cleaned, the user must be instructed to perform the required action on the appliance directly before retrying. This cannot be done remotely. See the example below for how to handle such cases. Handling User Action Requests Some tool responses may ask the user to perform a physical action that must be performed on the appliance directly and confirmed (e.g., "The coffee machine needs to (be cleaned|run the cleaning program|be descaled|run the Calc'n'Clean program). Please say [OK] if you'd like to continue with the selected program anyway.", "Please make sure no one is currently using your coffee machine and say [OK].", "Is the milk still fresh?", "Please close the door and say [OK]."). The tool response "Please enable remote start first." is an example of such a request. In this case, please ask the user to enable remote start on their appliance and/or in the Home Connect app, and then confirm with you once done. IMPORTANT: These confirmation requests cannot be automatically fulfilled via a tool call. They must be confirmed on the appliance directly. When you encounter such responses: 1. Parse the request: Extract what action the user needs to perform (e.g., "connect the milk container", "close the door") 2. Inform the user: Clearly explain what they need to do physically with their appliance 3. Wait for confirmation: Ask the user to confirm the action once they've completed the action and if you should retry the operation 4. Retry the operation: Only if the user confirms they performed the action and asks you to retry, retry the same tool call - the issue should be resolved If the same error or request persists when retryin…
coffeemaker_startBrewing
ChatGPTStart brewing a selected type of beverage such as coffee, espresso, or hot water. - The coffee maker needs to be powered on and ready. - Only the beverages returned by coffeemaker_getAvailableBeverages are supported, otherwise the tool will fail. - If the user's request does not exactly match a supported beverage, ask for clarification rather than guessing. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Input Parameters - Required: beverage (enum): The desired type of beverage as returned by coffeemaker_getAvailableBeverages. - Optional: size (enum): The beverage size between Small and ExtraLarge. The size is relative depending on the beverage. A volume in ml is not supported. - Optional: strength (enum): The coffee strength. The supported values depend on the beverage type. - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances. CRITICAL SAFETY REQUIREMENT - Multiple Beverage Handling: Coffee makers can brew exactly one (1) beverage at a time. When a user requests multiple beverages: 1. Brew the first beverage using this tool 2. STOP and wait - Do NOT call this tool again 3. Explicitly tell the user: "I've started brewing [beverage]. Please remove the cup when it's done and place a new cup, then let me know when you're ready for the next beverage." 4. Only proceed after the user explicitly confirms the cup has been replaced The same applies for rinse cycles: Always wait for user confirmation that a cup is in place after a rinse operation took place. Hard constraints: - This tool MUST NOT be called more than once in a single assistant response - Never assume the cup has been replaced - Never call this tool to brew again without explicit user confirmation Violating these rules will cause spills and overflow. Important: If the brew cannot be started because the coffee machine needs to be cleaned, the user must be instructed to perform the required action on the appliance directly before retrying. This cannot be done remotely. See the example below for how to handle such cases. Handling User Action Requests Some tool responses may ask the user to perform a physical action that must be performed on the appliance directly and confirmed (e.g., "The coffee machine needs to (be cleaned|run the cleaning program|be descaled|run the Calc'n'Clean program). Please say [OK] if you'd like to continue with the selected program anyway.", "Please make sure no one is currently using your coffee machine and say [OK].", "Is the milk still fresh?", "Please close the door and say [OK]."). The tool response "Please enable remote start first." is an example of such a request. In this case, please ask the user to enable remote start on their appliance and/or in the Home Connect app, and then confirm with you once done. IMPORTANT: These confirmation requests cannot be automatically fulfilled via a tool call. They must be confirmed on the appliance directly. When you encounter such responses: 1. Parse the request: Extract what action the user needs to perform (e.g., "connect the milk container", "close the door") 2. Inform the user: Clearly explain what they need to do physically with their appliance 3. Wait for confirmation: Ask the user to confirm the action once they've completed the action and if you should retry the operation 4. Retry the operation: Only if the user confirms they performed the action and asks you to retry, retry the same tool call - the issue should be resolved If the same error or request persists when retryin…
coffeemaker_stopBrewing
ChatGPTStop brewing the currently active beverage. If there is no active brew, the tool will fail. This does not power off the coffee maker. Important: Stopped brews cannot be resumed. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Note: Program names and settings in the response are already localized and should be preserved as-is when translating other parts of the response to the user's language. Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances.
coffeemaker_stopBrewing
ChatGPTStop brewing the currently active beverage. If there is no active brew, the tool will fail. This does not power off the coffee maker. Important: Stopped brews cannot be resumed. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Note: Program names and settings in the response are already localized and should be preserved as-is when translating other parts of the response to the user's language. Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances.
coffeemaker_stopBrewing
ChatGPTStop brewing the currently active beverage. If there is no active brew, the tool will fail. This does not power off the coffee maker. Important: Stopped brews cannot be resumed. Important error handling sequence: 1. Tool call fails or generic error response to "check the device" was returned -> IMMEDIATELY call [appliance]_getStatus 2. Provide helpful guidance based on the returned status 3. ALWAYS Provide helpful error messages while avoiding over-explaining Note: Program names and settings in the response are already localized and should be preserved as-is when translating other parts of the response to the user's language. Input Parameters - Optional: language (string): ISO 639-1 language code (e.g., 'en', 'de'). Use the language the user is speaking in. Defaults to 'en' if not provided. - Optional: haId (string): haId of the specific appliance. Only required if multiple appliances of the same type are present. Use haId as obtained from getAvailableAppliances.
getAvailableAppliances
ChatGPTRetrieves information about the Home Connect appliances of the user. Purpose Use this tool to discover which home appliances the user has connected to their Home Connect account and to determine which appliances are supported by this MCP server. Supported Appliance Types This MCP server currently supports only the following appliance types: - COFFEEMAKER Notes: - Only appliances within the Home Connect ecosystem can be interacted with using this MCP server. - The user may have other appliance types connected, but this server can only interact with supported types listed above, this includes that favorites can only be fetched and started for the supported appliance types. - Demo devices created in the Home Connect app are not supported. - Support for additional appliance types is actively being developed. Handling Unsupported Appliances When a user requests information about or attempts to control an unsupported appliance: 1. Required Response: Use this exact message format: "While we're working hard to deliver an awesome experience for all home appliances, yours is still unsupported. Right now we only support COFFEEMAKER, but more appliances are coming soon." 2. Suggest Alternatives: If the user has other supported appliances, recommend they try interacting with them instead. Best Practices - Always call this tool first before attempting to control any appliance - Verify support status for the specific appliance the user wants to control - Set clear expectations about current capabilities and limitations - Provide informative feedback when users request actions on unsupported appliances - Explicitly inform the user if an appliance is not supported or not connected - If the user has multiple appliances of the same type, ask which one they want to use before performing operations. - In case of issues provide helpful error messages while avoiding over-explaining. Output Schema The tool returns json data with the following structure: - appliances (array<object>): Array of home appliance objects containing information about available appliances in the user's home and whether they are supported by the assistant. Explicitly state to the user if an appliance is not supported or not connected. - haId (string): Internal Home Connect appliance ID used to identify the appliance. Do not show to the user. - name (string): Name of the appliance as set in the Home Connect App. - enumber (string): E-number of the appliance. Can be used to identify the appliance model for support purposes (e.g. searching for a user manual). Don't show to the user unless relevant for the users request. - type (string): Appliance type. - connected (boolean): Indicates whether the appliance is currently connected. - isSupportedByAssistant (boolean): Indicates whether the appliance is supported by the assistant.
getAvailableAppliances
ChatGPTRetrieves information about the Home Connect appliances of the user. Purpose Use this tool to discover which home appliances the user has connected to their Home Connect account and to determine which appliances are supported by this MCP server. Supported Appliance Types This MCP server currently supports only the following appliance types: - COFFEEMAKER Notes: - Only appliances within the Home Connect ecosystem can be interacted with using this MCP server. - The user may have other appliance types connected, but this server can only interact with supported types listed above, this includes that favorites can only be fetched and started for the supported appliance types. - Demo devices created in the Home Connect app are not supported. - Support for additional appliance types is actively being developed. Handling Unsupported Appliances When a user requests information about or attempts to control an unsupported appliance: 1. Required Response: Use this exact message format: "While we're working hard to deliver an awesome experience for all home appliances, yours is still unsupported. Right now we only support COFFEEMAKER, but more appliances are coming soon." 2. Suggest Alternatives: If the user has other supported appliances, recommend they try interacting with them instead. Best Practices - Always call this tool first before attempting to control any appliance - Verify support status for the specific appliance the user wants to control - Set clear expectations about current capabilities and limitations - Provide informative feedback when users request actions on unsupported appliances - Explicitly inform the user if an appliance is not supported or not connected - If the user has multiple appliances of the same type, ask which one they want to use before performing operations. - In case of issues provide helpful error messages while avoiding over-explaining. Output Schema The tool returns json data with the following structure: - appliances (array<object>): Array of home appliance objects containing information about available appliances in the user's home and whether they are supported by the assistant. Explicitly state to the user if an appliance is not supported or not connected. - haId (string): Internal Home Connect appliance ID used to identify the appliance. Do not show to the user. - name (string): Name of the appliance as set in the Home Connect App. - enumber (string): E-number of the appliance. Can be used to identify the appliance model for support purposes (e.g. searching for a user manual). Don't show to the user unless relevant for the users request. - type (string): Appliance type. - connected (boolean): Indicates whether the appliance is currently connected. - isSupportedByAssistant (boolean): Indicates whether the appliance is supported by the assistant.
getAvailableAppliances
ChatGPTRetrieves information about the Home Connect appliances of the user. Purpose Use this tool to discover which home appliances the user has connected to their Home Connect account and to determine which appliances are supported by this MCP server. Supported Appliance Types This MCP server currently supports only the following appliance types: - COFFEEMAKER Notes: - Only appliances within the Home Connect ecosystem can be interacted with using this MCP server. - The user may have other appliance types connected, but this server can only interact with supported types listed above, this includes that favorites can only be fetched and started for the supported appliance types. - Demo devices created in the Home Connect app are not supported. - Support for additional appliance types is actively being developed. Handling Unsupported Appliances When a user requests information about or attempts to control an unsupported appliance: 1. Required Response: Use this exact message format: "While we're working hard to deliver an awesome experience for all home appliances, yours is still unsupported. Right now we only support COFFEEMAKER, but more appliances are coming soon." 2. Suggest Alternatives: If the user has other supported appliances, recommend they try interacting with them instead. Best Practices - Always call this tool first before attempting to control any appliance - Verify support status for the specific appliance the user wants to control - Set clear expectations about current capabilities and limitations - Provide informative feedback when users request actions on unsupported appliances - Explicitly inform the user if an appliance is not supported or not connected - If the user has multiple appliances of the same type, ask which one they want to use before performing operations. - In case of issues provide helpful error messages while avoiding over-explaining. Output Schema The tool returns json data with the following structure: - appliances (array<object>): Array of home appliance objects containing information about available appliances in the user's home and whether they are supported by the assistant. Explicitly state to the user if an appliance is not supported or not connected. - haId (string): Internal Home Connect appliance ID used to identify the appliance. Do not show to the user. - name (string): Name of the appliance as set in the Home Connect App. - enumber (string): E-number of the appliance. Can be used to identify the appliance model for support purposes (e.g. searching for a user manual). Don't show to the user unless relevant for the users request. - type (string): Appliance type. - connected (boolean): Indicates whether the appliance is currently connected. - isSupportedByAssistant (boolean): Indicates whether the appliance is supported by the assistant.
startFavoriteProgram
ChatGPTStart the favorite program (e.g. the favorite beverage of a coffee maker or the favorite wash cycle of a dishwasher). - Requires the favorite ID. - Fails if the appliance is not ready. Note: Favorites can only be fetched and started for the supported appliance types. Use the getAvailableAppliances tool to check which appliances are supported. Input Parameters - Required: favoriteId (string): unique identifier of a saved favorite the user wants to start.
startFavoriteProgram
ChatGPTStart the favorite program (e.g. the favorite beverage of a coffee maker or the favorite wash cycle of a dishwasher). - Requires the favorite ID. - Fails if the appliance is not ready. Note: Favorites can only be fetched and started for the supported appliance types. Use the getAvailableAppliances tool to check which appliances are supported. Input Parameters - Required: favoriteId (string): unique identifier of a saved favorite the user wants to start.
startFavoriteProgram
ChatGPTStart the favorite program (e.g. the favorite beverage of a coffee maker or the favorite wash cycle of a dishwasher). - Requires the favorite ID. - Fails if the appliance is not ready. Note: Favorites can only be fetched and started for the supported appliance types. Use the getAvailableAppliances tool to check which appliances are supported. Input Parameters - Required: favoriteId (string): unique identifier of a saved favorite the user wants to start.
