Skip to main content
Glama

Launch an app, folder or document

launch

Open an app, folder, document, or Settings page and hand the foreground back to the user, returning each new window with proof of which request created it.

Instructions

Open an application (name, absolute path or Store app id, with its arguments), a folder or a document (absolute path) or a Settings page (ms-settings:...) and give the foreground back to the user. Returns the windows attributed to this launch, each with its proof: "process" (the process the shell returned), "folder" (a new Explorer window showing exactly that folder) or "application" (the requested application, started after the request: another instance started at the same moment could be taken for it; a Store app by its app id); other new windows come back as candidates (outcome unknown). Look at one before acting.

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": {
      "app": "<app>"
    },
    "name": "launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesApplication, folder, document or Settings page; a program may be followed by its arguments as a Windows command line ("C:\My Apps\app.exe" "C:\x\note.txt")
argsNoArguments of a program (.exe or application name), as a Windows command line, quoted like on the command line; never a switch for a Chromium/Electron application

Output Schema

NameRequiredDescriptionDefault
nextNo
boundNo
titleNo
hiddenNo
reasonNo
statusYesOutcome: opened, verified, unknown, prompted, unmet, sent-unconfirmed…
windowNo
windowsNoWindows attributed to this launch, with their proof
bindableNo
candidatesNoOther new windows (outcome unknown)
nativeWindowNo
foregroundReturnedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.7.4
    • addedInput schema / properties / app / description
      Added value: +"Application, folder, document or Settings page; a program may be followed by its arguments as a Windows command line (\"C:\\My Apps\\app.exe\" \"C:\\x\\note.txt\")"
    • addedInput schema / properties / args
      Added value: +{
      +  "description": "Arguments of a program (.exe or application name), as a Windows command line, quoted like on the command line; never a switch for a Chromium/Electron application",
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "bindable": {
      +      "type": "string"
      +    },
      +    "bound": {
      +      "type": "integer"
      +    },
      +    "candidates": {
      +      "description": "Other new windows (outcome unknown)",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "foregroundReturned": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "hidden": {
      +      "type": "boolean"
      +    },
      +    "nativeWindow": {
      +      "type": "integer"
      +    },
      +    "next": {
      +      "type": "string"
      +    },
      +    "reason": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "Outcome: opened, verified, unknown, prompted, unmet, sent-unconfirmed…",
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "window": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "windows": {
      +      "description": "Windows attributed to this launch, with their proof",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "status"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The description adds substantial behavioral context beyond the annotations: it explains foreground handoff, window attribution proofs, and uncertainty around candidate windows. It does not mention permissions or failure modes, so it is not a full 5.

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 front-loaded with the core action and is appropriately sized for a tool with several accepted input types. The single dense paragraph is slightly harder to parse than ideal but contains no obvious filler.

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?

Given the simple two-parameter schema and an output schema that documents returns, the description is largely complete. It adds useful attribution and uncertainty details, though it still leaves the relationship to sibling tools implicit.

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?

The schema already has 100% description coverage for both parameters, so the baseline is 3. The description reinforces accepted app forms and argument behavior but adds little syntax detail beyond the schema.

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 specific verb and resource: opening an application, folder, document, or Settings page. It does not explicitly differentiate itself from siblings like act, look, or window, so it falls short of a 5.

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 purpose, and the closing 'Look at one before acting' hints at a verification workflow. However, it does not explicitly say when to use this tool versus alternatives such as act or look.

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