Skip to main content
Glama
TrueOleg

MCP Mac Apps Server

by TrueOleg

open_application

Launch macOS applications by name using this MCP server tool. Open apps like Safari, Finder, or Calculator through voice or text commands.

Instructions

Открывает приложение на Mac по имени. Примеры: 'Safari', 'Finder', 'TextEdit', 'Calculator'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNameYesИмя приложения для запуска (например, 'Safari', 'Calculator')

Implementation Reference

  • Handler function that implements the 'open_application' tool logic by executing the macOS 'open -a' command to launch the specified application.
    private async openApplication(appName: string) {
      try {
        // Используем команду open для запуска приложения
        await execAsync(`open -a "${appName}"`);
        return {
          content: [
            {
              type: "text",
              text: `Приложение "${appName}" успешно запущено`,
            },
          ],
        };
      } catch (error) {
        throw new Error(
          `Не удалось запустить приложение "${appName}": ${error instanceof Error ? error.message : String(error)}`
        );
      }
    }
  • Handler function that implements the 'open_application' tool by running the shell command 'open -a "app_name"'.
    def open_application(app_name: str) -> str:
        """Opens application by name"""
        stdout, stderr = exec_command(f'open -a "{app_name}"')
        if stderr:
            raise Exception(f'Failed to launch application "{app_name}": {stderr}')
        return f'Application "{app_name}" successfully launched'
  • src/index.ts:57-70 (registration)
    Registration of the 'open_application' tool in the tools list, including description and input schema definition.
      name: "open_application",
      description:
        "Открывает приложение на Mac по имени. Примеры: 'Safari', 'Finder', 'TextEdit', 'Calculator'",
      inputSchema: {
        type: "object",
        properties: {
          appName: {
            type: "string",
            description: "Имя приложения для запуска (например, 'Safari', 'Calculator')",
          },
        },
        required: ["appName"],
      },
    },
  • src/server.py:46-58 (registration)
    Registration entry for 'open_application' tool with schema in get_tools() function.
        "name": "open_application",
        "description": "Opens an application on Mac by name. Examples: 'Safari', 'Finder', 'TextEdit', 'Calculator'",
        "inputSchema": {
            "type": "object",
            "properties": {
                "appName": {
                    "type": "string",
                    "description": "Application name to launch (e.g., 'Safari', 'Calculator')",
                },
            },
            "required": ["appName"],
        },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does (opens applications) but doesn't describe what happens if the app is already running, if the app name is invalid, if it requires specific permissions, or what the expected outcome looks like. For a system-level operation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 - a single sentence stating the purpose followed by relevant examples. Every element earns its place: the core functionality is stated upfront, and the examples provide immediate practical guidance without unnecessary elaboration. The structure is front-loaded with the primary action.

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 tool with good schema coverage but no annotations and no output schema, the description provides adequate basic context about what the tool does. However, it lacks important contextual information about error conditions, system requirements, or what constitutes success/failure. The examples help but don't compensate for missing behavioral transparency needed for a system operation tool.

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% with the single parameter 'appName' well-documented in the schema. The description adds value by providing concrete examples ('Safari', 'Finder', 'TextEdit', 'Calculator') that illustrate expected parameter values, but doesn't provide additional semantic context beyond what the schema already states about application names.

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 ('Открывает' - opens) and resource ('приложение на Mac по имени' - Mac application by name) with specific examples provided. It distinguishes from siblings like 'quit_application' and 'get_running_applications' by focusing on launching apps rather than closing or querying them. However, it doesn't explicitly differentiate from 'open_file_with_app' which has a different primary purpose.

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 implies usage context through examples of common Mac applications, suggesting this tool is for launching standard macOS apps. However, it provides no explicit guidance on when to use this versus alternatives like 'open_file_with_app' (which opens files with specific apps) or 'run_applescript' (which could also launch apps). No exclusion criteria or prerequisites are 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/TrueOleg/MCP-expirements'

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