Skip to main content
Glama
Sign In
Karagöz

Karagöz

by yagizdo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Open a URL

open_url

Opens a URL in the default handler or a specified app on Android and iOS devices, letting agents launch links during device automation.

Instructions

Open a URL in the app that handles it, or in the app named by app. On iOS it returns before the app is in front, and a simulator may first ask "Open in ?".

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

Input Schema

NameRequiredDescriptionDefault
appNoPackage name or bundle id; not on an iOS simulator.
urlYes
deviceNoId or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: on iOS it returns before the app is foregrounded, and simulators may show an 'Open in <app>?' confirmation. That is genuinely useful for interpreting results and timing. It does not describe failure behavior or what the call returns, keeping it short of 5.

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 with no filler, and the primary behavior is front-loaded before the platform caveats. Every clause carries information the agent would otherwise have to guess.

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?

With annotations covering the safety profile and no output schema to explain, the description supplies the key non-obvious platform behaviors an agent needs. Missing only error/return expectations and whether the target app must be installed, which are secondary for a fire-and-forget open action.

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% and the description only touches the 'app' parameter indirectly ('the app named by app'). The 'url' parameter has no schema description and the description never says which schemes (http, custom deep links) are acceptable, so the agent gains little beyond structured fields.

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 URL') and clarifies the default routing behavior ('in the app that handles it'), which separates it from device-control siblings like launch or tap. It does not explicitly name an alternative tool, so it stops short of a 5.

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 platform-specific notes (iOS simulator prompt) but there is no explicit when-to-use/when-not guidance or comparison to launch/install. The agent must infer that this is for deep links or custom URL schemes rather than app startup.

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