Skip to main content
Glama

launch_app_logs_sim

Launch an app in an iOS simulator and capture its logs for debugging and testing purposes.

Instructions

Launches an app in an iOS simulator and captures its logs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
simulatorUuidYesUUID of the simulator to use (obtained from list_simulators)
bundleIdYesBundle identifier of the app to launch (e.g., 'com.example.MyApp')
argsNoAdditional arguments to pass to the app

Implementation Reference

  • Registration of the 'launch_app_logs_sim' tool, including input schema (simulatorUuid, bundleId, optional args), handler that validates parameters, starts log capture with console enabled using startLogCapture helper, and returns the log session ID for further use.
    export function registerLaunchAppWithLogsInSimulatorTool(server: McpServer): void {
      server.tool(
        'launch_app_logs_sim',
        'Launches an app in an iOS simulator and captures its logs.',
        {
          simulatorUuid: z
            .string()
            .describe('UUID of the simulator to use (obtained from list_simulators)'),
          bundleId: z
            .string()
            .describe("Bundle identifier of the app to launch (e.g., 'com.example.MyApp')"),
          args: z.array(z.string()).optional().describe('Additional arguments to pass to the app'),
        },
        async (params): Promise<ToolResponse> => {
          const simulatorUuidValidation = validateRequiredParam('simulatorUuid', params.simulatorUuid);
          if (!simulatorUuidValidation.isValid) {
            return simulatorUuidValidation.errorResponse!;
          }
    
          const bundleIdValidation = validateRequiredParam('bundleId', params.bundleId);
          if (!bundleIdValidation.isValid) {
            return bundleIdValidation.errorResponse!;
          }
    
          log('info', `Starting app launch with logs for simulator ${params.simulatorUuid}`);
    
          // Start log capture session
          const { sessionId, error } = await startLogCapture({
            simulatorUuid: params.simulatorUuid,
            bundleId: params.bundleId,
            captureConsole: true,
          });
          if (error) {
            return {
              content: [createTextContent(`App was launched but log capture failed: ${error}`)],
              isError: true,
            };
          }
    
          return {
            content: [
              createTextContent(
                `App launched successfully in simulator ${params.simulatorUuid} with log capture enabled.\n\nLog capture session ID: ${sessionId}\n\nNext Steps:\n1. Interact with your app in the simulator.\n2. Use 'stop_and_get_simulator_log({ logSessionId: "${sessionId}" })' to stop capture and retrieve logs.`,
              ),
            ],
          };
        },
      );
    }
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 launching and logging but lacks details on behavioral traits such as whether this is a blocking operation, how logs are captured/formatted, error handling, or resource requirements, leaving significant gaps for a tool with mutation and logging capabilities.

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 single, efficient sentence that front-loads the core functionality ('Launches an app in an iOS simulator') and adds the key feature ('captures its logs') without any wasted words, making it highly concise and well-structured.

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?

Given the complexity of launching and logging with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., log output, success status), behavioral aspects, or error conditions, which are critical for effective use by an AI agent.

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%, providing clear documentation for all parameters. The description adds no additional parameter semantics beyond what the schema already covers, so it meets the baseline score of 3 without compensating or enhancing understanding.

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?

The description clearly states the action ('Launches an app'), target ('in an iOS simulator'), and additional function ('and captures its logs'), making the purpose specific and distinct from sibling tools like 'launch_app_sim' (which lacks logging) and 'start_sim_log_cap' (which only captures logs).

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 through parameter descriptions (e.g., 'simulatorUuid' from 'list_simulators'), but there's no explicit guidance on when to use this tool versus alternatives like 'launch_app_sim' or 'start_sim_log_cap', nor any prerequisites or exclusions mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SampsonKY/XcodeBuildMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server