mac-apps-launcher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_applicationsA | List all applications installed in the /Applications folder |
| launch_appB | Launch a Mac application by name |
| open_with_appB | Open a file or folder with a specific application |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: launch_app launches apps by name, list_applications lists installed apps, and open_with_app opens files/folders with apps. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (launch_app, list_applications, open_with_app) using snake_case throughout. This predictable naming scheme enhances readability and usability for agents.
With 3 tools, this server is well-scoped for its purpose of launching and managing Mac applications. Each tool earns its place by covering essential operations: listing apps, launching them, and opening files with them, without being too sparse or bloated.
The tool set provides complete coverage for the domain of Mac app launching and management. It includes discovery (list_applications), launching (launch_app), and file association (open_with_app), with no obvious gaps or dead ends for typical agent workflows.