Skip to main content
Glama

adb_mobile_data

Enable or disable mobile data on an Android device via ADB, optionally targeting a specific device serial.

Instructions

Enable or disable mobile data

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "enabled": "<enabled>"
    },
    "name": "adb_mobile_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
enabledYestrue = enable mobile data, false = disable

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: not whether root is required, whether the change persists across reboots, whether it disrupts an active connection, or what is returned. Only the direction of the toggle is clear from the parameter name.

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

Conciseness4/5

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

A single six-word phrase with zero filler, and the operative verb leads. It is efficient, though the brevity edges into under-specification rather than true tightness.

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

Completeness2/5

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

For a device-state mutation with no annotations and no output schema, the description should at least mention permission requirements and side effects on connectivity. The schema covers the two simple parameters, but nothing tells the agent what this call actually does to the device or its return value.

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

Parameters3/5

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

Schema description coverage is 100%, and both parameters ('device' serial and the 'enabled' boolean) are fully documented in the schema, so the baseline of 3 applies. The description adds no format, default, or per-device semantics beyond what the schema already states.

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

Purpose4/5

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

The description states a specific verb pair ('enable or disable') and resource ('mobile data'), so the action is unambiguous. It does not distinguish this from adjacent toggles in the sibling set (adb_wifi, adb_airplane_mode, adb_airplane_cycle), which an agent must resolve on its own.

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

Usage Guidelines2/5

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

There is no guidance on when to use this instead of adb_wifi or adb_airplane_mode, nor any stated preconditions such as root or privileged shell access. The agent is left to infer the entire selection context from the name.

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

Deploy Server

Other Tools