Device Tools

Device tools are used when a connected device exposes its own capabilities during a voice session. For example, a device can report sensor status, update a theme, restart itself, control lights, or run actions supported by its firmware.

Two Types Of Device Tools

Type	Used for
Device MCP	The device publishes its own tool list using MCP
Device IoT	The device publishes properties and control actions, such as turn on/off, set a value, or check status

Requirements

The device is registered and attached to an assistant.
The device is online during the voice session.
The firmware supports MCP or IoT descriptors.
Voice is enabled for the assistant.

How It Works In Voice

The device starts a voice session with Assistant Core.
If the device supports MCP, the server asks it for the available tools.
If the device provides IoT descriptors, properties and actions become tools.
When the user asks for a matching action, the assistant calls the tool through the device connection.
The device performs the action or returns data to the assistant.

Examples

User says	Device tool could run
“Turn on the living room light”	Call a light control action if supported by firmware
“What is the temperature now?”	Read a temperature sensor property
“Change the device theme”	Call a theme update tool if supported
“Restart the device”	Call a restart action if the firmware exposes one

Check Device Tools

In some device screens, Assistant Core can send MCP commands such as tools/list or tools/call to inspect capabilities exposed by the device.

If tools do not appear:

Check that the device is online.
Check that the firmware supports MCP or IoT descriptors.
Check that the device is attached to the correct assistant.
Restart the device after updating firmware.

Device tools depend on firmware. Two devices of the same board type may expose different capabilities if they run different firmware.