Skip to main content
Glama

Launch App

launch_app

Launch a Python GUI script or system app with auto-focus and portal session binding, terminating any existing instance first to start a fresh, focused process.

Instructions

Launches a Python GUI script or system app with auto-focus and portal session binding.

If restart=True or if the app is already running, gracefully terminates the old process and launches a fresh instance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
cwdNo
argsNo
targetYes
restartNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior1/5

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

The annotations declare destructiveHint=false, but the description says the tool 'gracefully terminates the old process' when restart=True or the app is already running. That is a destructive side effect that could cause unsaved work to be lost, contradicting the annotation and potentially misleading an agent about safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two front-loaded sentences with little waste. The second sentence is essential for restart behavior, though the first sentence could be slightly tighter.

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?

For a mutation tool with four parameters and 0% schema description coverage, the definition is incomplete. It covers the core launch and restart behavior but leaves cwd and args unexplained and does not address permissions or side effects beyond termination.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain four parameters. It identifies target as a Python GUI script or system app and explains restart behavior, but cwd and args are not described at all, leaving two parameters undocumented.

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 states a specific verb, 'Launches', and concrete resources, a Python GUI script or system app. Auto-focus and portal session binding add useful specialization, but it does not explicitly distinguish this from sibling tools like restart_app or terminate_app.

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?

It explains the restart=True condition and the already-running case, which gives implied usage guidance. However, it does not state when to choose launch_app versus restart_app, terminate_app, or other app-management siblings.

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