Skip to main content
Glama
eugenechen0514

mac-apps-launcher

list_applications

Read-onlyIdempotent

Discover and display all applications installed in the /Applications folder on a Mac system using this command-line tool for quick access and organization.

Instructions

List all applications installed in the /Applications folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • tools.ts:38-47 (handler)
    The tool handler callback that calls the listApplications helper, formats the app list as a numbered string, and returns it as a text content result.
    cb: async () => {
      const apps = await listApplications();
      const appListString = apps.reduce((acc, app, index) => {
        return `${acc}${index + 1}. ${app}\n`;
      }, "");
      const toolResult: CallToolResult = {
        content: [{ type: "text", text: appListString }],
      };
      return toolResult;
    },
  • tools.ts:9-9 (schema)
    Input schema for the list_applications tool (empty object as it requires no input parameters).
    export const ListApplicationsInputSchema = {};
  • tools.ts:103-107 (registration)
    Registration of the list_applications tool config (along with others) in the exported tools array.
    export const tools: ToolConfig<any>[] = [
      listApplicationsConfig,
      launchAppConfig,
      openWithAppConfig,
    ];
  • Helper function imported and used by the tool handler to retrieve the list of .app files from /Applications directory.
    export async function listApplications(): Promise<string[]> {
      try {
        const files = await readdir("/Applications");
        return files.filter((file) => file.endsWith(".app")).sort();
      } catch (error) {
        console.error("Error listing applications:", error);
        return [];
      }
    }
  • tools.ts:27-48 (registration)
    Definition of the tool configuration object for list_applications, including name, description, annotations, schema reference, and inline handler callback.
    const listApplicationsConfig: ToolConfig<typeof ListApplicationsInputSchema> = {
      name: "list_applications",
      description: "List all applications installed in the /Applications folder",
      annotations: {
        title: "列出所有應用程式",
        readOnlyHint: true, // 只讀取應用程式列表,不修改系統
        destructiveHint: false, // 不執行任何破壞性操作
        idempotentHint: true, // 重複呼叫會得到相同結果(若應用程式列表未變)
        openWorldHint: false, // 只與本機檔案系統互動,不連接外部系統
      },
      schema: ListApplicationsInputSchema,
      cb: async () => {
        const apps = await listApplications();
        const appListString = apps.reduce((acc, app, index) => {
          return `${acc}${index + 1}. ${app}\n`;
        }, "");
        const toolResult: CallToolResult = {
          content: [{ type: "text", text: appListString }],
        };
        return toolResult;
      },
    };
Behavior4/5

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

The description adds valuable context beyond annotations by specifying the scope ('/Applications folder'), which annotations don't cover. Annotations already declare readOnlyHint=true, destructiveHint=false, etc., so the description appropriately supplements rather than contradicts them.

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 that front-loads the core purpose ('List all applications') and adds necessary scope detail ('installed in the /Applications folder') with zero wasted words.

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

Completeness4/5

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

For a simple read-only tool with no parameters and good annotations, the description is mostly complete. However, without an output schema, it could benefit from mentioning the return format (e.g., list of app names/paths), though the scope detail partially compensates.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description confirms no parameters are needed, as it describes a simple listing operation without any filtering or options.

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

Purpose5/5

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

The description clearly states the specific action ('List all applications') and resource ('installed in the /Applications folder'), distinguishing it from siblings like 'launch_app' and 'open_with_app' which perform different operations on applications.

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 by specifying '/Applications folder', but provides no explicit guidance on when to use this tool versus alternatives like 'launch_app' or 'open_with_app', nor any prerequisites or exclusions.

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/eugenechen0514/mac-apps-launcher'

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