Skip to main content
Glama
Sign In
Karagöz

Karagöz

by yagizdo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Launch an app

launch

Start an installed app by package name on a connected Android or iOS device or emulator, opening it as the device's home screen icon would; on iOS, it may return before the app is in front.

Instructions

Start an app as its launcher icon does. On iOS it returns before the app is in front.

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": {
      "package": "<package>"
    },
    "name": "launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoId or name.
packageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already establish that this is not read-only but also not destructive, and the description adds important behavioral context: on iOS it returns before the app is actually in the foreground. That async/platform-specific detail is valuable for an agent, though other details such as foregrounding behavior or failure modes are omitted.

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 tightly written sentences. The core purpose is front-loaded and the platform caveat follows without any filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity tool with annotations and no output schema, the description is adequate but leaves meaningful gaps: whether the app must be installed, how `device` defaults, and what launch success/failure looks like. It provides helpful iOS timing context but could be more complete for an agent invoking it.

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?

Schema coverage is only 50%, with the required `package` parameter lacking any schema description. The tool description does not explain that this should be an app package identifier or clarify default device behavior, so it does not compensate for the schema gap.

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 and resource: start an app, with the useful semantic equivalent of behaving like its launcher icon. It is clear what the tool does, though it does not explicitly contrast itself with siblings such as install, terminate, or uninstall.

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 launcher-icon analogy: use this to start an installed app. However, there is no explicit guidance on when to use this versus alternatives, nor on prerequisites such as whether the app must already be installed.

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