Skip to main content
Glama

launch

Start an app, document, or URL without moving focus away from the user's active window or task.

Instructions

Start an app, document or URL without it taking the user's focus.

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
appYespath, App Paths name (notepad, excel), document or URL
argsNocommand-line arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the side-effecting, open-world nature is known. The description's genuine addition is the 'without taking the user's focus' guarantee, which is real behavioral context; however it says nothing about failure handling, whether it waits for startup, or how success is observable.

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 sentence, front-loaded with the action and its allowed inputs, with the scope qualifier placed last where it belongs. Nothing is redundant.

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 two-parameter launch tool with full schema coverage and annotations covering safety, the description supplies the action and its most important behavioral promise. The remaining gap, whether the call blocks until the app is ready or returns a handle, is minor for a tool with no output schema.

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% and both parameters carry their own descriptions, so the schema already defines the accepted forms of app and args. The description only restates the resource kinds in prose without adding format, resolution, or argument-quoting semantics, so baseline 3 applies.

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 (start) plus the exact resource set it accepts (app, document or URL) and adds a distinguishing behavioral trait: the launched item does not take the user's focus. That trait separates it from siblings like window or ui_act without needing to open their schemas.

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 verb and the non-focus-stealing qualifier, which hints this is the background-launch path, but there is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no named alternative for cases where the app should be brought to the foreground.

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