Skip to main content
Glama
Sign In
adb-ai

adb-ai

by cyberpunk2183
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adb_scan

Scan the local network for devices with an open ADB port to find Android devices when their IP changes under DHCP or when no device appears connected.

Instructions

Scan the local network for devices with the adb port open. Use when a device's IP changed (DHCP) or nothing is connected.

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

Input Schema

NameRequiredDescriptionDefault
subnetNoprefix such as 192.168.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It explains that this scans the local network for open adb ports, but does not state whether scanning attempts connections, expected runtime, permissions needed, or side effects. Minimum viable for a read-like network scan.

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 with no filler; the primary action is front-loaded and the usage condition follows immediately. Every sentence earns its place.

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 simple one-parameter scan tool without an output schema, the description tells the agent what it does and when to use it. It could add a note about default behavior when subnet is omitted, but the schema already covers that parameter.

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%, so the subnet parameter is already documented with an example. The description adds no parameter-specific detail beyond what the schema provides, which is the baseline for high schema coverage.

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 ('Scan'), resource ('local network'), and target condition ('devices with the adb port open'). It implicitly distinguishes itself from connection/list tools like adb_list_devices and adb_connect, though it does not name a sibling explicitly.

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

Usage Guidelines4/5

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

It gives clear triggering conditions: use when a device's IP changed via DHCP or when nothing is connected. It does not mention when not to use it or name specific alternatives, but the context for invocation is explicit.

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