Skip to main content
Glama
atom2ueki

MCP Server for iOS Simulator

terminate-simulator-session

Ends an active iOS simulator session by providing the session ID, ensuring controlled shutdown via the MCP Server for integrated simulator management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYes

Implementation Reference

  • MCP tool registration for 'terminate-simulator-session', including input schema and handler function that delegates to simulatorManager.terminateSession
    this.server.tool(
      'terminate-simulator-session',
      {
        sessionId: z.string()
      },
      async ({ sessionId }) => {
        fileLogger.info(`Terminating simulator session: ${sessionId}`);
        try {
          const success = await simulatorManager.terminateSession(sessionId);
          
          if (!success) {
            return {
              content: [{
                type: 'text',
                text: `Failed to terminate session: ${sessionId}`
              }],
              isError: true
            };
          }
          
          return {
            content: [{
              type: 'text',
              text: `Session terminated: ${sessionId}`
            }]
          };
        } catch (error) {
          fileLogger.error(`Failed to terminate simulator session: ${sessionId}`, { error });
          return {
            content: [{
              type: 'text',
              text: `Error: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Handler function for the MCP tool that logs, calls simulatorManager.terminateSession, and returns success/error response
    async ({ sessionId }) => {
      fileLogger.info(`Terminating simulator session: ${sessionId}`);
      try {
        const success = await simulatorManager.terminateSession(sessionId);
        
        if (!success) {
          return {
            content: [{
              type: 'text',
              text: `Failed to terminate session: ${sessionId}`
            }],
            isError: true
          };
        }
        
        return {
          content: [{
            type: 'text',
            text: `Session terminated: ${sessionId}`
          }]
        };
      } catch (error) {
        fileLogger.error(`Failed to terminate simulator session: ${sessionId}`, { error });
        return {
          content: [{
            type: 'text',
            text: `Error: ${error instanceof Error ? error.message : String(error)}`
          }],
          isError: true
        };
      }
  • Zod input schema requiring sessionId string
    sessionId: z.string()
  • Core implementation that checks if simulator is running, shuts it down if needed via shutdownSimulator, removes session from map, and returns success/failure
    async terminateSession(sessionId: string): Promise<boolean> {
      const session = this.sessions.get(sessionId);
      if (!session) {
        fileLogger.warn(`Session not found: ${sessionId}`);
        return false;
      }
    
      try {
        // Try to get the simulator status
        let isRunning = false;
        try {
          const status = await session.simulator.stat();
          isRunning = status.state === 'Booted';
        } catch (statError) {
          // If we can't get status, check the booted simulators list
          fileLogger.warn(`Failed to get simulator status, checking booted simulators`, { statError });
          const bootedSimulators = await this.getBootedSimulators();
          isRunning = bootedSimulators.some(sim => sim.udid === session.udid);
        }
        
        // Shutdown the simulator if running
        if (isRunning) {
          fileLogger.info(`Shutting down simulator for session: ${sessionId}`);
          await this.shutdownSimulator(sessionId);
        } else {
          fileLogger.info(`Simulator already shut down for session: ${sessionId}`);
        }
        
        // Remove from sessions map
        this.sessions.delete(sessionId);
        
        fileLogger.info(`Session terminated: ${sessionId}`);
        return true;
      } catch (error) {
        fileLogger.error(`Failed to terminate session: ${sessionId}`, { error });
        return false;
      }
    }
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