Skip to main content
Glama
Sign In
computer-use

computer-use

by Cassius-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

launch_app

Launch one or multiple macOS applications by name, bundle ID, or path in the background without stealing focus, with an option to activate and bring them to the foreground.

Instructions

Launch one or multiple macOS applications by name, bundle ID, or .app path (launches in the background by default without stealing focus unless activate=true).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "launch_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoApplication name (e.g. 'Calculator', 'Notes'), bundle ID ('com.apple.Notes'), or path.
appsNoMultiple applications to launch in parallel in one call.
activateNoBring launched application(s) to foreground (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the non-obvious focus behavior (background launch, no focus stealing unless activate=true), but says nothing about what happens if the app is already running, what errors occur for an unresolvable name/bundle ID, or whether macOS automation/accessibility permissions are required.

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?

A single front-loaded sentence: verb, resource, accepted identifiers, then the default-behavior caveat in a parenthetical. No filler and nothing buried.

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 simple three-parameter launch tool this is close to adequate, but with no output schema and no annotations the description leaves the agent guessing about return values, failure modes, and permission prerequisites. It covers the happy path well and the edge cases not at all.

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%, so each of the three parameters is already documented, and the description largely restates that content (identifiers, background-by-default, activate). Baseline 3 applies; it adds no format, precedence, or conflict-handling detail beyond the schema.

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?

States a specific verb ('Launch') and resource ('macOS applications'), and enumerates the three accepted identifier forms (name, bundle ID, .app path). An agent can immediately tell this apart from list_apps or manage_windows, which read or manipulate rather than start apps.

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?

Usage is implied by the identifier forms and the multi-app 'apps' array, but there is no explicit when-to-use versus when-not guidance and no mention of siblings such as list_apps for discovering app names. The single-vs-multiple distinction is only hinted at through the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools