Skip to main content
Glama

open_uri

Open URIs on Android devices to launch apps, websites, or content directly from the espresso-mcp server.

Instructions

Open a URI on the connected Android device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYes

Implementation Reference

  • The handler function for the 'open_uri' tool. It uses adb to start an Android intent to view the given URI on the connected device.
    @mcp.tool()
    def open_uri(uri: str) -> str:
        """Open a URI on the connected Android device"""
        result = subprocess.run(
            ["adb", "shell", "am", "start", "-a", "android.intent.action.VIEW", "-d", uri],
            capture_output=True,
            text=True,
        )
        if result.returncode != 0:
            raise RuntimeError(f"Error opening URI '{uri}': {result.stderr}")
        return f"URI '{uri}' has been opened successfully."
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action but lacks details on permissions needed, potential side effects (e.g., app launches), error handling, or response format. This is a significant gap for a device interaction 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?

The description is a single, direct sentence with zero wasted words, making it highly efficient and front-loaded. Every word contributes to understanding the tool's core function.

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?

Given the complexity of device operations, no annotations, no output schema, and incomplete parameter guidance, the description is insufficient. It doesn't cover behavioral aspects like what happens on success/failure, making it inadequate for safe and effective use.

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?

The description implies the 'uri' parameter is used to specify what to open, but with 0% schema description coverage and no additional details (e.g., format examples like 'http://' or 'content://'), it adds minimal value beyond the schema's basic structure. The baseline is 3 due to the single parameter.

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 clearly states the action ('Open') and target resource ('a URI on the connected Android device'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from siblings like 'start_app' or 'tap', which might also involve device interactions, so it doesn't reach the highest score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., device connectivity), exclusions, or compare it to siblings like 'start_app' for app-specific URIs, leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vs4vijay/espresso-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server