Skip to main content
Glama

adb_airplane_mode

Toggle airplane mode on or off to reset cellular registration during radio testing and control network connectivity on Android devices.

Instructions

Toggle airplane mode on/off. Useful for resetting cellular registration during radio testing.

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_airplane_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
enabledYestrue = enable airplane mode, 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

B3.2/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 burden. It doesn't disclose whether airplane mode also disables Wi-Fi/Bluetooth, whether root or permissions are required, whether the change persists across reboots, or any error behavior — significant gaps for a device-mutating radio tool.

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?

Two short sentences with the purpose front-loaded and no filler. It could be marginally tighter given the second sentence is context rather than instruction.

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

Completeness3/5

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

For a simple two-parameter tool with a fully described schema and no output schema, the definition is close to adequate. It is nonetheless thin for a state-changing device tool with zero annotations, leaving modem/connectivity side effects and the cycle alternative unexplained.

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 coverage is 100%, with both `device` and `enabled` fully documented, so the schema does the heavy lifting. The description adds no semantics beyond it, and its word "toggle" slightly conflicts with the explicit boolean `enabled` parameter, which sets state rather than flipping it.

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?

States a specific verb and resource ("Toggle airplane mode on/off") and adds a scoping note about radio testing. It is cleanly distinguishable from most siblings, though it never mentions adb_airplane_cycle, the nearest alternative, so differentiation is only partial.

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

Usage Guidelines3/5

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

"Useful for resetting cellular registration during radio testing" implies a usage context but is not an explicit when-to-use rule. It gives no exclusion or pointer to adb_airplane_cycle, adb_wifi, or adb_mobile_data, which an agent would need to choose correctly.

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