Skip to main content
Glama

phone_open_link

Opens a web page or deep link (https, app scheme, geo, mailto) on an Android device; optionally specify a package to force a specific app.

Instructions

Open a web page or a deep link on the phone (https://…, myapp://…, geo:lat,lng?q=…, mailto:…). package= forces a specific app (e.g. com.android.chrome).

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": "phone_open_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
packageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose genuinely behavioral facts beyond the schema: that non-HTTP schemes (deep links) are accepted and that package= forces dispatch to a specific handler app. It says nothing about what happens when no handler exists, whether the call blocks until the page loads, or what the result indicates — meaningful gaps for a device-side action tool.

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 sentences, zero filler; the core action is front-loaded and the accepted URI forms and package override are packed into tight parentheticals. Nothing could be removed without losing information.

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 two-parameter tool with no output schema and no annotations, the description covers both parameters and the accepted input protocols sufficiently for an agent to invoke it correctly. The remaining omission is error/return semantics, which is a modest rather than disqualifying gap at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it largely does: it explains that url accepts web URLs, custom schemes, geo: URIs, and mailto: links, and that package pins the receiving app with a concrete example (com.android.chrome). What is not stated is whether package is a partial/short name or must be a fully qualified component.

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 and resource ("Open a web page or a deep link") and enumerates concrete URI forms (https://, myapp://, geo:, mailto:), which makes the resource unambiguous. It does not name the closest sibling, phone_open_app, so the boundary (open a URL vs. launch an app package directly) is left for the agent to infer.

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 URI scheme examples implicitly convey when this tool applies, and the parenthetical about package= hints at the app-launching alternative without naming it. There is no explicit when-not guidance, e.g. what to do if the agent only has a package name and no URL, which is precisely where phone_open_app would be the alternative.

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