adb-ai

Overview Schema Source Related Servers Discussions Admin

adb_set_timer

Start a countdown timer in an Android device's clock app via ADB by specifying duration and optional label or target device.

Instructions

Start a countdown timer in the device's clock app.

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": {
      "duration": "<duration>"
    },
    "name": "adb_set_timer"
  }
}

Input Schema

Name	Required	Description
`label`	No
`device`	No	serial, ip[:port] or saved alias; omit to use the default device
`duration`	Yes	10m, 1h30m, 90s

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 27, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations exist, so the description carries the full burden. It says the timer is created 'in the device's clock app' but omits whether this launches the app, overwrites an existing timer, requires an active device connection, or what confirmation is returned—significant gaps for a mutation-like action.

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?

A single front-loaded sentence with zero waste. It is efficiently structured, though its brevity is more under-specification than true conciseness.

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?

With three parameters, no annotations, and no output schema, a one-line description is not enough. It does not explain side effects, app-launch behavior, or what happens with the label and device parameters.

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 67%: the required duration parameter has format examples ('10m, 1h30m, 90s') and device is documented, but label is bare in both schema and description. The description adds no parameter-level meaning beyond the schema.

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?

States a specific verb ('Start') and resource ('countdown timer'), and 'countdown timer' implicitly distinguishes it from the sibling adb_set_alarm. Clear without needing to open the schema, though it does not explicitly name the sibling it differs from.

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?

Usage is implied by the resource type: a countdown timer versus an alarm (adb_set_alarm). There is no explicit when-to-use statement, no prerequisites, and no named alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.