Skip to main content
Glama
Sign In
adb-ai

adb-ai

by cyberpunk2183
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adb_open_url

Opens a URL or deep link on a connected Android device via ADB, with optional app and device targeting so links open in the intended place.

Instructions

Open a URL or deep link, optionally in a specific 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": {
      "url": "<url>"
    },
    "name": "adb_open_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNo
urlYes
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

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and discloses almost nothing: not whether the URL opens in the default browser, what happens with an unknown package, whether the device must be unlocked, or what the response looks like. For a device-side action tool with zero annotation coverage this is a significant gap.

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?

A single short sentence with no filler, and the core action is front-loaded. Nothing could be trimmed without losing information.

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 no annotations, no output schema, and one of three parameters undocumented, the description is too thin to let an agent call this confidently. It should at minimum clarify the app identifier format and note failure behavior when the app or URL cannot be handled.

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?

Only the device parameter has a schema description (33% coverage), so the description must compensate for url and app. It implies app is an app selector but never says whether it is a package name, alias, or display name, and adds no deep-link syntax or format notes for url beyond what the schema already conveys.

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 gives a specific verb+resource (open a URL/deep link) plus an optional qualifier (in a specific app), which is enough to distinguish it from adb_open_app in most cases. It stops short of naming that sibling explicitly, so the boundary is inferred rather than stated.

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?

The phrase 'optionally in a specific app' hints at the relationship with adb_open_app, so usage is implied. There is no explicit when-to-use/when-not guidance and no mention of what happens if the target app is not installed or the URL is malformed.

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