Skip to main content
Glama
TrueOleg

MCP Mac Apps Server

by TrueOleg

get_running_applications

Retrieve a list of all currently running applications on macOS to monitor active processes and manage system resources.

Instructions

Получает список всех запущенных приложений на Mac

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • TypeScript handler function that uses AppleScript via osascript to fetch and format the list of currently running Mac applications (non-background processes).
    private async getRunningApplications() {
      try {
        // Получаем список запущенных приложений через AppleScript
        const { stdout } = await execAsync(
          `osascript -e 'tell application "System Events" to get name of every application process whose background only is false'`
        );
        
        const apps = stdout
          .trim()
          .split(", ")
          .map((app) => app.trim())
          .filter((app) => app.length > 0);
    
        return {
          content: [
            {
              type: "text",
              text: `Запущенные приложения:\n${apps.join("\n")}`,
            },
          ],
        };
      } catch (error) {
        throw new Error(
          `Не удалось получить список приложений: ${error instanceof Error ? error.message : String(error)}`
        );
      }
    }
  • Python handler function that uses AppleScript via osascript to fetch and format the list of currently running Mac applications (non-background processes).
    def get_running_applications() -> str:
        """Gets list of running applications"""
        apple_script = 'tell application "System Events" to get name of every application process whose background only is false'
        stdout, stderr = exec_command(f'osascript -e \'{apple_script}\'')
        if stderr:
            raise Exception(f"Failed to get list of applications: {stderr}")
    
        apps = [app.strip() for app in stdout.strip().split(", ") if app.strip()]
        return "Running applications:\n" + "\n".join(apps)
  • TypeScript tool schema definition including name, description, and empty input schema (no parameters required).
      name: "get_running_applications",
      description: "Получает список всех запущенных приложений на Mac",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Python tool schema definition including name, description, and empty input schema (no parameters required).
        "name": "get_running_applications",
        "description": "Gets list of all running applications on Mac",
        "inputSchema": {
            "type": "object",
            "properties": {},
        },
    },
  • src/index.ts:311-312 (registration)
    TypeScript dispatch/registration in the CallToolRequestSchema handler that routes to the getRunningApplications method.
    case "get_running_applications":
      return await this.getRunningApplications();
  • src/server.py:597-598 (registration)
    Python dispatch/registration in the tools/call handler that calls the get_running_applications function.
    elif tool_name == "get_running_applications":
        result_text = get_running_applications()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe how it behaves: no information on permissions needed, whether it's safe or destructive, rate limits, output format, or error handling. This is a significant gap for a tool with zero annotation coverage.

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 in Russian that directly states the tool's purpose without any fluff or redundant information. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 (a read operation with no parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., list format, data included), potential errors, or system dependencies, leaving gaps for the agent to handle this tool effectively.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't mention parameters, which aligns with the schema. A baseline of 4 is applied since no parameter information is needed or missing.

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 verb 'получает' (gets) and the resource 'список всех запущенных приложений на Mac' (list of all running applications on Mac), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'open_application' or 'quit_application' that also deal with applications, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'open_application' or 'quit_application'. It lacks any context about prerequisites, timing, or exclusions, leaving the agent to infer usage from the purpose alone.

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