Skip to main content
Glama
Sign In
simctl-mcp-server

simctl-mcp-server

by nzrsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

simctl_launch_app

Launch an app on a simulator device via bundle ID. Configure debugger wait, console mode, and launch arguments.

Instructions

Launch an app on a simulator device.

Args: device: Device UDID, name, or 'booted' for current device bundle_id: App bundle identifier wait_for_debugger: Wait for debugger to attach before launching console_mode: Console output mode (none, console, console-pty) args: Additional launch arguments

Returns: Launch result

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": {
      "device": "<device>",
      "bundle_id": "<bundle_id>"
    },
    "name": "simctl_launch_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYes
bundle_idYes
wait_for_debuggerNo
console_modeNonone
argsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior fully. It mentions wait_for_debugger and console_mode, but does not explain side effects (e.g., app state after launch), error scenarios, or whether the device must be booted. Major behavioral traits like these are missing.

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 well-structured docstring with a clear one-line purpose, followed by Args and Returns sections. Each sentence provides necessary information without redundancy, making it efficient and easy to parse.

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?

The description covers purpose and parameter semantics adequately, but lacks important context: prerequisites (e.g., device booted, app installed), error handling, and detailed return value. Given the tool's complexity and no output schema, more context would be beneficial.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description provides meaningful explanations for all 5 parameters: device accepts UDID/name/'booted', bundle_id is an identifier, wait_for_debugger is a boolean, console_mode options are listed, and args are additional arguments. This significantly enriches the schema.

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 states 'Launch an app on a simulator device', which clearly identifies the verb and resource. It differentiates from siblings like install or terminate apps, though it does not explicitly contrast them. The parameter list further clarifies the tool's scope.

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 like simctl_install_app or simctl_terminate_app. It does not specify prerequisites (e.g., device must be booted) or contexts where launching is appropriate.

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