Skip to main content
Glama

boot_sim

Start an iOS simulator by providing its UUID to enable testing and development of iOS applications.

Instructions

Boots an iOS simulator. IMPORTANT: You MUST provide the simulatorUuid parameter. Example: boot_sim({ simulatorUuid: 'YOUR_UUID_HERE' })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
simulatorUuidYesUUID of the simulator to use (obtained from list_simulators)

Implementation Reference

  • The core handler function for the 'boot_sim' tool. Validates the simulatorUuid parameter, executes 'xcrun simctl boot' command, handles success/error responses, and provides next-step instructions.
        async (params): Promise<ToolResponse> => {
          const simulatorUuidValidation = validateRequiredParam('simulatorUuid', params.simulatorUuid);
          if (!simulatorUuidValidation.isValid) {
            return simulatorUuidValidation.errorResponse!;
          }
    
          log('info', `Starting xcrun simctl boot request for simulator ${params.simulatorUuid}`);
    
          try {
            const command = ['xcrun', 'simctl', 'boot', params.simulatorUuid];
            const result = await executeCommand(command, 'Boot Simulator');
    
            if (!result.success) {
              return {
                content: [
                  {
                    type: 'text',
                    text: `Boot simulator operation failed: ${result.error}`,
                  },
                ],
              };
            }
    
            return {
              content: [
                {
                  type: 'text',
                  text: `Simulator booted successfully. Next steps:
    1. Open the Simulator app: open_sim({ enabled: true })
    2. Install an app: install_app_sim({ simulatorUuid: "${params.simulatorUuid}", appPath: "PATH_TO_YOUR_APP" })
    3. Launch an app: launch_app_sim({ simulatorUuid: "${params.simulatorUuid}", bundleId: "YOUR_APP_BUNDLE_ID" })
    4. Log capture options:
       - Option 1: Capture structured logs only (app continues running):
         start_sim_log_cap({ simulatorUuid: "${params.simulatorUuid}", bundleId: "YOUR_APP_BUNDLE_ID" })
       - Option 2: Capture both console and structured logs (app will restart):
         start_sim_log_cap({ simulatorUuid: "${params.simulatorUuid}", bundleId: "YOUR_APP_BUNDLE_ID", captureConsole: true })
       - Option 3: Launch app with logs in one step:
         launch_app_logs_sim({ simulatorUuid: "${params.simulatorUuid}", bundleId: "YOUR_APP_BUNDLE_ID" })`,
                },
              ],
            };
          } catch (error) {
            const errorMessage = error instanceof Error ? error.message : String(error);
            log('error', `Error during boot simulator operation: ${errorMessage}`);
            return {
              content: [
                {
                  type: 'text',
                  text: `Boot simulator operation failed: ${errorMessage}`,
                },
              ],
            };
          }
  • Input schema using Zod for the 'boot_sim' tool, defining the required 'simulatorUuid' string parameter.
      simulatorUuid: z
        .string()
        .describe('UUID of the simulator to use (obtained from list_simulators)'),
    },
  • Local registration function that registers the 'boot_sim' tool on the MCP server, including name, description, input schema, and handler.
    export function registerBootSimulatorTool(server: McpServer): void {
      server.tool(
        'boot_sim',
        "Boots an iOS simulator. IMPORTANT: You MUST provide the simulatorUuid parameter. Example: boot_sim({ simulatorUuid: 'YOUR_UUID_HERE' })",
        {
          simulatorUuid: z
            .string()
            .describe('UUID of the simulator to use (obtained from list_simulators)'),
        },
        async (params): Promise<ToolResponse> => {
          const simulatorUuidValidation = validateRequiredParam('simulatorUuid', params.simulatorUuid);
          if (!simulatorUuidValidation.isValid) {
            return simulatorUuidValidation.errorResponse!;
          }
    
          log('info', `Starting xcrun simctl boot request for simulator ${params.simulatorUuid}`);
    
          try {
            const command = ['xcrun', 'simctl', 'boot', params.simulatorUuid];
            const result = await executeCommand(command, 'Boot Simulator');
    
            if (!result.success) {
              return {
                content: [
                  {
                    type: 'text',
                    text: `Boot simulator operation failed: ${result.error}`,
                  },
                ],
              };
            }
    
            return {
              content: [
                {
                  type: 'text',
                  text: `Simulator booted successfully. Next steps:
    1. Open the Simulator app: open_sim({ enabled: true })
    2. Install an app: install_app_sim({ simulatorUuid: "${params.simulatorUuid}", appPath: "PATH_TO_YOUR_APP" })
    3. Launch an app: launch_app_sim({ simulatorUuid: "${params.simulatorUuid}", bundleId: "YOUR_APP_BUNDLE_ID" })
    4. Log capture options:
       - Option 1: Capture structured logs only (app continues running):
         start_sim_log_cap({ simulatorUuid: "${params.simulatorUuid}", bundleId: "YOUR_APP_BUNDLE_ID" })
       - Option 2: Capture both console and structured logs (app will restart):
         start_sim_log_cap({ simulatorUuid: "${params.simulatorUuid}", bundleId: "YOUR_APP_BUNDLE_ID", captureConsole: true })
       - Option 3: Launch app with logs in one step:
         launch_app_logs_sim({ simulatorUuid: "${params.simulatorUuid}", bundleId: "YOUR_APP_BUNDLE_ID" })`,
                },
              ],
            };
          } catch (error) {
            const errorMessage = error instanceof Error ? error.message : String(error);
            log('error', `Error during boot simulator operation: ${errorMessage}`);
            return {
              content: [
                {
                  type: 'text',
                  text: `Boot simulator operation failed: ${errorMessage}`,
                },
              ],
            };
          }
        },
      );
    }
  • Global tool registration configuration for 'boot_simulator' tool, imported from simulator.ts and enabled via environment variable.
      register: registerBootSimulatorTool,
      groups: [ToolGroup.SIMULATOR_MANAGEMENT, ToolGroup.IOS_SIMULATOR_WORKFLOW],
      envVar: 'XCODEBUILDMCP_TOOL_BOOT_SIMULATOR',
    },

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the required parameter but doesn't disclose behavioral traits like whether booting is idempotent, what happens if the simulator is already running, whether this requires specific permissions, or what the expected outcome is. The description adds minimal behavioral context beyond the basic action.

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 extremely concise and front-loaded with the core purpose. The two sentences both earn their place - the first states what the tool does, the second provides critical usage guidance with a clear example. Zero wasted words.

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 single-parameter action tool with no annotations and no output schema, the description provides the minimum viable information: what it does and the required parameter. However, it lacks context about what 'booting' entails operationally, what happens on success/failure, or how this relates to other simulator management tools.

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 the schema already fully documents the single parameter. The description emphasizes that the parameter is mandatory and provides an example format, but doesn't add meaningful semantic context beyond what's in the schema description ('UUID of the simulator to use (obtained from list_simulators)').

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 ('Boots') and target resource ('an iOS simulator'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'open_sim' or 'launch_app_sim', but the verb 'Boots' suggests starting/initializing the simulator itself rather than opening an interface or launching an app.

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?

The description provides some usage guidance by emphasizing the mandatory simulatorUuid parameter and referencing list_simulators as the source for this value. However, it doesn't explicitly state when to use this tool versus alternatives like 'open_sim' or 'launch_app_sim', nor does it mention prerequisites or timing considerations.

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