Skip to main content
Glama

adb_wifi

Enable or disable Wi-Fi on Android devices through ADB, with an optional device serial to target a specific connected device.

Instructions

Enable or disable WiFi

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
enabledYestrue = enable WiFi, 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 bears the full burden of behavioral disclosure. It says nothing about whether root or special permissions are required on Android, whether existing connections drop, whether the setting persists, or how failures surface — all material for a state-changing radio toggle.

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?

Four words, front-loaded with the action and resource, with zero filler. It is efficient rather than padded; the only criticism is that terseness shades into under-specification, which is penalized in completeness.

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?

The tool is conceptually simple and its two parameters are fully documented, but with no annotations and no output schema the description should mention root/privilege requirements and any side effects of toggling the radio. As written, an agent lacks the information to call this safely on a device without root.

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%: 'device' is documented as a device serial and 'enabled' as the boolean toggle, so the description adds no parameter meaning beyond the schema. Baseline 3 applies since the schema already does the work.

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 names a specific action pair ('Enable or disable') and a specific resource ('WiFi'), so an agent knows exactly what state change this tool performs. It does not explicitly contrast itself with nearby siblings such as adb_wifi_firmware, adb_airplane_mode, or adb_mobile_data, which keeps it from a 5.

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 prefer this tool over adb_airplane_mode or adb_mobile_data, and no stated prerequisites or context for calling it. The agent must infer usage entirely 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