Skip to main content
Glama
Sign In
adb-mcp

adb-mcp

by FlashZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_airplane_mode

Toggle Android airplane mode via ADB by updating settings and broadcasting the change; root may be needed on newer Android versions.

Instructions

Toggle airplane mode (settings + broadcast). May need root on newer Android.

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": "set_airplane_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialNo
enabledYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the root requirement on newer Android and the settings+broadcast mechanism, but omits whether the change is reversible, what happens to existing wifi/cellular state, and confirmation/error behavior.

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?

Two short sentences, no filler, with the primary action front-loaded ahead of the caveat.

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?

An output schema exists so return values need not be explained, but for a mutation tool with zero annotation coverage and 0% parameter descriptions, the definition leaves the serial argument and the exact effect of 'enabled' unexplained. Adequate on the basics, thin on the rest.

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

Parameters2/5

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

Schema description coverage is 0% and the description documents neither the nullable 'serial' selector nor how 'enabled' should be interpreted. Calling it 'toggle' while the schema takes an explicit 'enabled' boolean further muddies the semantics of the one required parameter.

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 (toggle) and resource (airplane mode), and the parenthetical 'settings + broadcast' clarifies the two mechanisms applied. It is clearly distinguishable from nearby siblings like set_wifi and set_mobile_data.

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 tool versus alternatives (e.g. set_wifi / set_mobile_data for connectivity changes), nor any stated preconditions. The root caveat is a permission note, not usage routing.

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