Skip to main content
Glama

adb_airplane_cycle

Toggles airplane mode on and off after a set delay to force cellular re-registration for radio diagnostics and network testing.

Instructions

Cycle airplane mode on then off after a delay. Forces cellular re-registration — useful for radio diagnostics and network testing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adb_airplane_cycle"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
delaySecondsNoSeconds to keep airplane mode on (1-60, default 3)

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

A3.5/5.0
Behavior3/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 usefully discloses the key behavioral trait that connectivity is dropped and the radio re-registers, but it does not say whether the prior radio state is restored, what happens if the device is offline or the toggle fails, or whether it blocks for the full delay.

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 tight sentences, front-loaded with the action and followed by the rationale. Nothing is padded, though the purpose clause could be slightly tighter.

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 two-parameter, no-output-schema device action, the description covers what it does, why, and the timing control via the schema. The main gap is the post-condition after the cycle (whether airplane mode is guaranteed off and the radio restored), which matters for a connectivity-disrupting tool.

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%, with both device and delaySeconds documented including bounds and default. The description only echoes the delay notion ('after a delay'), adding no syntax or device-selection guidance beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource (cycle airplane mode on then off) plus the mechanism (delay) and effect (forces cellular re-registration). It is clearly distinct from the sibling adb_airplane_mode in practice, though it never names that sibling or states the contrast explicitly.

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?

It names two use cases (radio diagnostics, network testing), which implies when to reach for it. However, with siblings like adb_airplane_mode, adb_mobile_data and adb_network_scan in the same family, it gives no explicit guidance on when this cycler is preferred over setting airplane mode directly, and no prerequisites or exclusions.

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