Skip to main content
Glama
Sign In
adb-ai

adb-ai

by cyberpunk2183
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adb_state

Checks the foreground app, screen power state, and media playback on an Android device so you can verify that an action worked.

Instructions

What is in the foreground, whether the screen is on, and whether media is playing. Call this to check an action worked.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoserial, ip[:port] or saved alias; omit to use the default device

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?

With no annotations, the description carries full burden: it implies a non-mutating query and discloses what state is reported, which is the key behavioral fact. It does not address return shape, multi-device behavior, or any cost/latency considerations.

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, contents first and the call trigger second, with no filler. Every clause 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 single-param observation tool with no output schema, the description tells the agent what information comes back and when to call it. Adding the exact return field names would make it complete, but nothing essential is missing.

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?

Only one optional parameter and schema coverage is 100%, so the schema fully documents the device selector. The description adds nothing beyond it, which matches the baseline for high-coverage schemas.

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?

Names the specific resource and enumerates its contents: foreground app, screen power state, media playback. Clearly a read/observe tool, distinguishable from the action siblings (adb_tap, adb_open_app, etc.), though it never names an alternative 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?

'Call this to check an action worked' gives a concrete trigger that fits the sibling set of action tools. It does not state exclusions or name specific alternatives, but the verification use case is unambiguous.

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