Robot Actions — Remote Device Control

android_devtools_mock_add

Add (or update in place, when id matches an existing route) a mock/abort rule for Chrome/WebView requests on this device. mode "mock" (default) serves the given status/headers/body without the request leaving the device; mode "abort" fails it so the page sees a network error. Routes apply immediately and survive navigation. WEB CONTENT ONLY: this intercepts requests made by browser/WebView pages. Requests made by native app code are NOT intercepted and never will be by this tool. Nothing device-wide is changed and no certificate is installed — the effect is scoped to the page. For requests made by native app code use android_traffic_mock_add instead.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Route id to update in place; omit to auto-generate a new one
`body`	No	Response body for mode "mock" (text, or base64 when bodyEncoding is "base64")
`mode`	No	"mock" serves a canned response (default); "abort" fails the request
`udid`	Yes	Device id (Android serial or iOS UDID)
`method`	No	Optional HTTP method filter (e.g. "GET"/"POST"); matches any method when omitted
`pageId`	No	Pin routing to a specific page id (from the *_list_pages tool). Omit to follow the active page automatically across navigations and new tabs — recommended.
`socket`	No	Abstract unix socket name (default: chrome_devtools_remote)
`status`	No	HTTP status to serve for mode "mock" (default 200)
`delayMs`	No	Latency injected before responding/failing, in ms (clamped to 60s)
`enabled`	No	Whether the route is active (default true) — disabled routes are kept but ignored
`headers`	No	Response headers for mode "mock", as {headerName: value} — e.g. {"content-type": "application/json"}. On iOS a `charset` in content-type is NOT applied to the response: an HTML body with non-ASCII characters must declare it in the document (e.g. <meta charset="utf-8">) or it will be decoded with the default encoding and render as mojibake.
`matchUrl`	Yes	URL pattern to match against the request's full URL
`matchType`	No	How matchUrl is interpreted against the request URL (default "contains")
`bodyEncoding`	No	Encoding of `body` (default "text")

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations, the description fully covers behavioral traits: modes (mock/abort), effect scope (web content only, no device-wide change, no certificate installed), immediacy, navigation survival, and the idle field recommendation. No contradictions.

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?

All sentences are valuable and front-loaded. The description starts with the core action and then efficiently adds critical distinctions (update capability, modes, scope, native app alternative) without redundancy. Appropriate length for 14 parameters.

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

Completeness4/5

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

For a complex tool with 14 parameters, no output schema, and no annotations, the description covers purpose, scope, modes, parameter usage, and alternatives thoroughly. Minor omission: no explicit mention of what the tool returns (e.g., route ID) but this is acceptable given lack of output schema requirement.

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

Parameters5/5

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

While schema coverage is 100%, the description adds substantial context for many parameters: id for update, mode differences, pageId recommendation, bodyEncoding base64, headers iOS charset caveat, delayMs clamping, matchType defaults. This far exceeds baseline 3.

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?

The description clearly states it adds or updates a mock/abort rule for Chrome/WebView requests on the device. It distinguishes from sibling tools like android_traffic_mock_add (for native code) and other platform-specific mock tools, and notes the scope is web content only.

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

Usage Guidelines5/5

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

Explicitly states when to use (for browser/WebView requests) and when not (native app code), directs to android_traffic_mock_add as alternative, and explains the update behavior when id matches an existing route.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0

Disambiguation2/5

The set contains near-identical duplicate families: web_* and playwright_* expose ~15 pairs of the same desktop-grid-browser operations (web_get_text/playwright_get_text, web_reload/playwright_reload), and screenshot/log/network/mock capabilities each have 5-8 entry points (device_screenshot vs android_mjpeg_screenshot vs ios_screenshot vs ios_fast_screenshot vs web_screenshot vs webpage_screenshot vs session_screenshot). Many individual descriptions carefully draw boundaries (devtools vs traffic, HID vs session), but an agent cannot reliably distinguish web_* from playwright_*, and ios_screenshot/ios_fast_screenshot/ios_mjpeg_screenshot blur together.

Naming Consistency2/5

The prefix scheme is broken: Android functionality is split arbitrarily between android_* and device_* (device_screenshot vs android_mjpeg_screenshot), the desktop browser gets two parallel prefixes (web_* and playwright_*), and verbs vary across equivalents (device_navigate_url vs web_navigate vs ios_safari_navigate). session_* uses bare verbs (session_url, session_back), and the same concept gets different names (ios_clipboard_get_hid vs ios_get_pasteboard; device_screen vs ios_orientation).

Tool Count1/5

333 tools is an extreme count by any measure — far beyond the 50+ threshold — and much of the bulk is duplicative (the web_*/playwright_* pairs alone double ~15 slots) or out-of-scope for a device-control server (TestRail, Jira, AzDO, agent memory, secret variables, feedback). Even granting that remote device control + test automation is a broad domain, this surface will devastate agent context budgets and is impossible to navigate coherently.

Completeness4/5

The core device-control and test-automation domain is remarkably thorough: Android and iOS each have full interaction, app-lifecycle, file, network/proxy, performance, crash, accessibility, recording, and replay coverage, with CRUD lifecycles for flows, suites, app uploads, TestRail cases, and visual-review baselines. Minor gaps exist at the margins — Jira/AzDO lack update/transition/comment operations, and iOS cannot open/close tabs — but the central workflows have no dead ends.

Resources

Need Help?