Fleet (tiny.technology MCP)

use_device and the other fleet tools, mounted only when TINY_MCP=1 — with the self-refusal guard — tools/tiny_mcp.py, 1 tool.

From the module docstring

tiny.technology fleet bridge — the tiny-tech MCP server as Strands tools.

tool	does
use_device	Reach the owner's OTHER devices on tiny.technology (fomo the arm, q-the-brain, the Mac, the other robot, the Sticky e-ink via the Mac, the iPhone).

use_device

use_device(
    action: str,
    device_id: Optional[str] = None,
    prompt: Optional[str] = None,
    wait: bool = True,
    envelope_id: Optional[str] = None,
) -> Dict[str, Any]

Reach the owner's OTHER devices on tiny.technology (fomo the arm, q-the-brain, the Mac, the other robot, the Sticky e-ink via the Mac, the iPhone). action='list' shows every device with online presence + capabilities — check it before saying a device is unavailable. action='invoke' (device_id, prompt) asks that device's own agent to do something and returns its answer (~45 s; a slow task returns pending:true + envelope_id, read it back with action='result'). You can NOT invoke yourself, and the device you invoke cannot relay further. Never pass wait=False unless the user asked for background work.

argument	meaning
action	list | invoke | result
device_id	target device id from list (invoke)
prompt	what the device should do (invoke)
wait	wait up to ~45 s for the answer (invoke, default True)
envelope_id	pending ticket to read (result)

source: tools/tiny_mcp.py:339