Robot Actions — Remote Device Control

App upload

app_upload

Upload an app build (.apk/.ipa) to your App Library. Send the file in chunks: base64-encode at most 50MB of the file per call as fileData, with chunkIndex (0-based) and totalChunks; the build is registered when the last chunk arrives. A file up to 50MB may be sent in one call without chunkIndex/totalChunks. .ipa files are re-signed for your devices on the way in unless skipResign is true. Returns the id that app_install uses; an automated test session references the same build as its app capability "ra-app://".

Input Schema

TableJSON Schema

Name	Required	Description
`fileData`	Yes	Base64-encoded file data — at most 50MB decoded per call
`fileName`	Yes	File name (e.g. "myapp.apk" or "myapp.ipa")
`userEmail`	No	User email for file ownership (defaults to the authenticated user)
`chunkIndex`	No	Chunk index (0-based) for chunked uploads
`skipResign`	No	Keep an .ipa exactly as uploaded (it is already signed for the target devices)
`totalChunks`	No	Total number of chunks for chunked uploads

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 22, 2026

addedInput schema / properties / chunkIndex / minimum
```
Added value: +0
```
changedInput schema / properties / chunkIndex / type
```
Previous value: -"number"New value: +"integer"
```

changedInput schema / properties / fileData / description

Previous value: -"Base64-encoded file data (max ~100MB per chunk)"New value: +"Base64-encoded file data — at most 50MB decoded per call"

addedInput schema / properties / skipResign

Added value: +{
+  "description": "Keep an .ipa exactly as uploaded (it is already signed for the target devices)",
+  "type": "boolean"
+}

addedInput schema / properties / totalChunks / minimum
```
Added value: +1
```
changedInput schema / properties / totalChunks / type
```
Previous value: -"number"New value: +"integer"
```

First observedAug 4, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial behavior beyond the annotations: 50MB decoded-per-call cap, 0-based chunk ordering, that registration occurs only when the last chunk arrives, and that .ipa files are re-signed on the way in unless skipResign is true. Annotations only give safety hints; the description supplies the actual operational semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then the chunking mechanics, the single-call shortcut, re-signing behavior, and return value in sequence. Every sentence carries distinct information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex chunked-upload mutation with no output schema, the description fully specifies size limits, chunk protocol, re-signing, and what the return value is (the id used by app_install and referenced as 'ra-app://<id>'). Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the 3 baseline applies, but the description adds inter-parameter logic the schema does not — how chunkIndex/totalChunks must be paired, and that a sub-50MB file needs neither. This exceeds what the individual field descriptions convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Upload an app build (.apk/.ipa) to your App Library' — and clearly distinguishes this from sibling install/list/delete operations. An agent immediately knows this is the ingest step that precedes app_install.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It establishes the workflow relationship ('Returns the id that app_install uses') and explains the single-call vs. chunked condition, which tells the agent when to supply chunkIndex/totalChunks. No explicit exclusions or when-not-to-use guidance, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Robot Actions — Remote Device Control tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?