ZennoDroid: device in ProjectMaker vs ERIUS PHONE

ZennoDroid: device in ProjectMaker tools

No tool names declared yet. Check the project README from the listing page.

ERIUS PHONE tools 21

• list_devicesList every Android device your API key can access, with live status (booted, Android version, screen size). Call this first to get device ids.
• whoamiShow which ERIUS PHONE account (tenant) and key id this server is using, and the device ids it can access. Handy to check the API key works.
• get_deviceGet full status of one device: boot state, Android version, screen size, and the app currently in the foreground. Omit `device` to use the default.
• snapshotGet an accessibility-tree snapshot of the current screen: every visible element with its text, role, and a `ref` id you can pass to tap/type/scroll. This is how the agent 'sees' the phone — read it before acting, and take a fresh one after any action since refs reset on every snapshot.
• screenshotTake a screenshot of the device screen right now and return it as an image you can look at, plus one line of text with the image size and the device's real screen size. The default is a JPEG whose longest side is 1024 px (tens of KB). A full-size PNG of a 1440x3120 phone is about 3 MB, which is more than many MCP clients accept in a tool result, so ask for it only when you need it: format="png", max_side=None. `format` is "jpeg", "webp" or "png"; `quality` is 1-100 (jpeg/webp); `max_side` caps the longest side in pixels (64-8192); `scale` (0.1-1) shrinks by a factor instead. When the image is smaller than the screen, pass its size as image_width/image_height to tap(), long_press() or swipe() so x,y are read in the image's pixels. Prefer snapshot() when you only need text and refs: it's far smaller.
• foregroundGet just the foreground app: package, activity, and whether a crash dialog is showing. Cheaper than a full snapshot when you only need this.
• tapTap an element. Prefer `ref` from a snapshot(), or `text`/`content_desc` to tap by visible label. Falls back to raw `x`,`y` pixel coordinates: in device pixels, or, with `image_width` and `image_height`, in the pixels of a screenshot of that size (the API maps the point to the screen).
• long_pressLong-press an element (e.g. to open a context menu or start a drag). Targets work like tap(): `ref`, `text`/`content_desc`, or raw `x`,`y` (with `image_width`/`image_height` when they come from a scaled screenshot). `ms` (hold time, default 800) only applies to the x,y form.
• type_textType text into a field. Optionally tap a `ref` or `text_target` label first to focus the field, `clear` the existing value, or press Enter after. Keystrokes sent while the field is still opening are lost, so if tapping the field opens a new screen (e.g. a search page), tap it first, wait for it with snapshot() or wait_for_text(), then type with no target. Check the result with snapshot(). Only printable ASCII is supported (adb limitation).
• press_keyPress a hardware/navigation key: back, home, enter, delete, tab, escape, up, down, left, right, space, power, volup, voldown, recent, menu, wakeup.
• swipeSwipe from one point to another: in device pixel coordinates, or, with `image_width` and `image_height`, in the pixels of a screenshot of that size.
• scrollScroll a list/container up, down, left, or right. `ref` must be the ref of the scrollable container itself (a ScrollView or List line in the snapshot), not of a row inside it: scrolling a single row does nothing. If the container has no ref, use swipe() instead.
• +9 more on the listing page