Skip to main content
Glama
atom2ueki

MCP Server for iOS Simulator

terminate-app

Forcefully close a specific app on an iOS simulator by providing the session ID and bundle ID, ensuring clean app termination for testing or debugging purposes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bundleIdYes
sessionIdYes

Implementation Reference

  • Registration of the 'terminate-app' MCP tool, including input schema (sessionId, bundleId) and inline handler that delegates to simulatorManager.terminateApp and formats MCP response.
    this.server.tool(
      'terminate-app',
      {
        sessionId: z.string(),
        bundleId: z.string()
      },
      async ({ sessionId, bundleId }) => {
        fileLogger.info(`Terminating app on simulator: ${sessionId}`, { bundleId });
        try {
          const success = await simulatorManager.terminateApp(sessionId, bundleId);
          
          if (!success) {
            return {
              content: [{
                type: 'text',
                text: `Failed to terminate app on session: ${sessionId}`
              }],
              isError: true
            };
          }
          
          return {
            content: [{
              type: 'text',
              text: `App terminated on session: ${sessionId}`
            }]
          };
        } catch (error) {
          fileLogger.error(`Failed to terminate app on session: ${sessionId}`, { error });
          return {
            content: [{
              type: 'text',
              text: `Error: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Core handler logic in SimulatorManager: retrieves simulator session and calls session.simulator.terminateApp(bundleId) from appium-ios-simulator library.
    async terminateApp(sessionId: string, bundleId: string): Promise<boolean> {
      const session = this.sessions.get(sessionId);
      if (!session) {
        fileLogger.warn(`Session not found: ${sessionId}`);
        return false;
      }
    
      try {
        await session.simulator.terminateApp(bundleId);
        fileLogger.info(`App terminated on simulator for session: ${sessionId}`);
        return true;
      } catch (error) {
        fileLogger.error(`Failed to terminate app for session: ${sessionId}`, { error });
        return false;
      }
    }
  • Zod schema for 'terminate-app' tool inputs: sessionId (string), bundleId (string).
    {
      sessionId: z.string(),
      bundleId: z.string()
    },
  • Type definition for the underlying simulator.terminateApp method called by the manager.
    terminateApp(bundleId: string): Promise<void>;
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