> For the complete documentation index, see [llms.txt](https://docs.orchard.airoverflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.orchard.airoverflow.com/mcp/tools.md).

# Tools

Every device tool takes a `selector` (uuid / uuid-prefix / name / tag), the same as the SDK and CLI.

## Discovery

| tool                    | does                                                                   |
| ----------------------- | ---------------------------------------------------------------------- |
| `list_sandboxes`        | List reachable devices (name, uuid, platform, state, tag). Start here. |
| `get_sandbox(selector)` | Full detail of one device.                                             |

## Lifecycle

| tool                      | does           |
| ------------------------- | -------------- |
| `start_sandbox(selector)` | Boot a device. |
| `stop_sandbox(selector)`  | Stop a device. |

## Input

| tool                                                                               | does                                                                     |
| ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| `tap(selector, x, y)`                                                              | Tap at pixel `(x, y)`.                                                   |
| `swipe(selector, x1, y1, x2, y2, ms=300)`                                          | Drag / scroll.                                                           |
| `key(selector, name)`                                                              | Press `home`/`back`/`recents`/`power`/`volup`/`voldown`/`enter`/….       |
| `type_text(selector, text)`                                                        | Type into the focused field.                                             |
| `tap_text(selector, text)`                                                         | Find an element by its label and tap it.                                 |
| `launch_app(selector, package)`                                                    | Launch by package id (Android) / bundle id (iOS).                        |
| `launch_intent(selector, package, component, action=None, data=None, extras=None)` | Start an exported activity component (Android). Refused if not exported. |

## See the screen

| tool                                        | does                                                                                 |
| ------------------------------------------- | ------------------------------------------------------------------------------------ |
| `screenshot(selector)`                      | Capture the screen as an image. The agent reads coordinates straight off it.         |
| `logs_tail(selector, lines=50, timeout=10)` | Recent device log lines (bounded by `timeout`, so it never hangs on a quiet device). |

## Apps

| tool                               | does                                                           |
| ---------------------------------- | -------------------------------------------------------------- |
| `list_apps(selector)`              | Installed apps/packages.                                       |
| `install_app(selector, path)`      | Install an `.apk`/`.ipa` from a local path on the server host. |
| `uninstall_app(selector, package)` | Uninstall by package id.                                       |

## Files

| tool                                           | does                                         |
| ---------------------------------------------- | -------------------------------------------- |
| `push_file(selector, local_path, dest_dir)`    | Upload a local file into a device directory. |
| `pull_file(selector, remote_path, local_path)` | Download a device file to a local path.      |

## Frida

| tool                                                 | does                                                     |
| ---------------------------------------------------- | -------------------------------------------------------- |
| `frida_status(selector)`                             | Report frida-server state.                               |
| `frida_install(selector)`                            | Install frida-server and start it. Slow.                 |
| `frida_start(selector)` / `frida_stop(selector)`     | Start or stop frida-server.                              |
| `frida_verify(selector, process=None)`               | Attach and trace a process to prove frida works.         |
| `frida_inject(selector, script, process, timeout=6)` | Run a frida script, return its `messages`. Android only. |

`frida_inject` returns once, after the run. For a live message stream, use the SDK `frida.stream` or the CLI `orchard frida stream`.

## Metadata

| tool                                 | does                                                           |
| ------------------------------------ | -------------------------------------------------------------- |
| `set_tag(selector, tag, color=None)` | Set the device's tag (plus an optional `#rrggbb` chip colour). |
| `create_snapshot(selector, name)`    | Snapshot the device.                                           |
| `restore_snapshot(selector, name)`   | Restore to a named snapshot.                                   |

`install_app` and `push_file` read from the filesystem of the machine running the server; `pull_file` writes there.

Next: [workflows](/mcp/workflows.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.orchard.airoverflow.com/mcp/tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.