Skip to main content
Glama
Sign In
twiddle-mcp

twiddle-mcp

by roti-c137
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

launch_app

Launch an iOS or Android app using its bundle ID or package name. Optionally terminate the app first if already running.

Instructions

Launch an app by iOS bundle id or Android package name.

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": {
      "appId": "<appId>"
    },
    "name": "launch_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesBundle id (com.example.App) or package name (com.example.app)
deviceNoDevice id from list_devices. Optional when exactly one device is booted.
relaunchNoTerminate first if already running

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, description carries full burden. It only says 'Launch an app' with no disclosure of side effects, permission requirements, or behavior when app already running (though schema has relaunch param). Minimal behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, very concise. However, could be slightly expanded to include key usage details while remaining efficient.

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?

Description does not mention necessary steps like list_devices to obtain device id, conditions for optional device, or behavior of relaunch. Lack of completeness given the tool's complexity and sibling context.

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 description coverage is 100%, so baseline 3. Description adds no extra meaning beyond what schema already provides for appId; device and relaunch parameters lack additional context in description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Launch an app by iOS bundle id or Android package name,' which identifies the specific verb (Launch) and resource (app) and distinguishes it from sibling tools like terminate_app or tap.

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?

No guidance on when to use vs alternatives, prerequisites (e.g., use list_devices to get device id), or when not to use. The description only states what the tool does without context.

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