Skip to main content
Glama
atom2ueki

MCP Server for iOS Simulator

shutdown-simulator-by-udid

Shutdown an iOS simulator by its unique device identifier (UDID) using a programmatic interface provided by the MCP Server for iOS Simulator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidYes

Implementation Reference

  • MCP tool registration for 'shutdown-simulator-by-udid', including input schema { udid: z.string() } and handler that calls simulatorManager.directShutdownByUDID and verifySimulatorShutdown
    this.server.tool(
      'shutdown-simulator-by-udid',
      {
        udid: z.string()
      },
      async (params) => {
        fileLogger.info(`Shutting down simulator directly by UDID: ${params.udid}`);
        try {
          const success = await simulatorManager.directShutdownByUDID(params.udid);
          
          if (!success) {
            return {
              content: [{
                type: 'text',
                text: `Failed to shutdown simulator with UDID: ${params.udid}`
              }],
              isError: true
            };
          }
          
          // Verify shutdown
          const verifySuccess = await simulatorManager.verifySimulatorShutdown(params.udid);
          
          if (!verifySuccess) {
            return {
              content: [{
                type: 'text',
                text: `Simulator shutdown command executed but simulator may still be running. UDID: ${params.udid}`
              }],
              isError: true
            };
          }
          
          return {
            content: [{
              type: 'text',
              text: `Simulator with UDID: ${params.udid} successfully shut down`
            }]
          };
        } catch (error) {
          fileLogger.error(`Failed to shutdown simulator by UDID: ${params.udid}`, { error });
          return {
            content: [{
              type: 'text',
              text: `Error: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Core handler function that executes the shutdown command via xcrun simctl shutdown ${udid}
    async directShutdownByUDID(udid: string): Promise<boolean> {
      fileLogger.info(`Attempting direct CLI shutdown for simulator: ${udid}`);
      try {
        const execAsync = promisify(exec);
        await execAsync(`xcrun simctl shutdown ${udid}`);
        fileLogger.info(`Direct CLI shutdown command completed for simulator: ${udid}`);
        return true;
      } catch (error) {
        fileLogger.error(`Failed direct CLI shutdown for simulator: ${udid}`, { error });
        return false;
      }
    }
  • Helper function to verify the simulator has been shut down by checking booted simulators list
    async verifySimulatorShutdown(udid: string): Promise<boolean> {
      try {
        // Get all booted simulators
        const bootedSimulators = await this.getBootedSimulators();
        
        // Check if our UDID is still in the list of booted simulators
        const stillRunning = bootedSimulators.some(sim => sim.udid === udid);
        
        if (stillRunning) {
          fileLogger.warn(`Simulator ${udid} is still reported as running`);
          return false;
        } else {
          fileLogger.info(`Verified simulator ${udid} is shut down`);
          return true;
        }
      } catch (error) {
        fileLogger.error(`Failed to verify simulator shutdown status: ${udid}`, { error });
        return false;
      }
    }
  • Zod input schema for the tool: requires 'udid' string parameter.
    {
      udid: z.string()
    },
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Related 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/atom2ueki/mcp-server-ios-simulator'

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