Skip to main content
Glama

Glasswarp

by com.glasswarp

app.launch

Destructive

Launch an executable on the remote Windows rig (name on PATH or absolute path), optional args. Side effects: starts a process; Glasswarp tracks it and closes it on session.end. Use for notepad.exe, mspaint.exe, chrome with URL args, etc. Wait/re-observe after launch before clicking — do not assume the window is focused immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoProcess args, e.g. ["--new-window", "https://example.com"]
session_idYesActive session id
path_or_nameYesExecutable name (e.g. notepad.exe) or absolute path

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesFalse when the tool failed
messageYesHuman-readable result for the agent

TDQS

A4.2/5.0
Behavior4/5

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

Describes side effects (starts process, tracked by Glasswarp, closed on session.end) and warns about focus assumption. Annotations already indicate destructiveHint and openWorldHint, so description adds useful context beyond annotations.

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?

Two sentences, no fluff. Front-loads the action and parameter info, then adds crucial usage guidance. Every sentence earns its place.

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?

With output schema present (not shown but mentioned), description explains side effects, use cases, and post-launch behavior. Sufficient for the tool's complexity.

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?

All three parameters have schema descriptions (coverage 100%). Description adds context about optional args and mentions 'name on PATH or absolute path', which is already in the schema. Examples provide slight additional clarity but no essential new information.

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?

Clearly states the action (launch) and resource (executable on remote Windows rig), with examples like notepad.exe, mspaint.exe. Distinguishes from sibling tools which are mostly input/screen/session related.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit use cases (notepad.exe, chrome with URL args) and a post-launch behavior warning (do not assume window focused). However, does not explicitly state when not to use or alternatives.

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

All Glasswarp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: session management, input methods, screen observation, demo retrieval, and rig listing. Descriptions explicitly state when to prefer one over another (e.g., click_target over click_xy, send_actions over chaining). No two tools overlap in functionality.

Naming Consistency5/5

All tools follow the domain.verb_noun pattern (e.g., app.launch, input.click_target, session.start) with consistent snake_case. Verbs like launch, list, get, click, send, type, observe are clear actions, and the naming is predictable across the entire set.

Tool Count5/5

16 tools cover the full spectrum of remote desktop control: 2 for demos, 1 for rigs, 4 for sessions, 1 for screen, 7 for input, and 1 for app launching. Each tool is necessary and there is no redundancy; the count is well-scoped for the domain.

Completeness5/5

The tool set provides a complete lifecycle for remote desktop interaction: rig selection, session start/end, screen observation, all common input actions (click, type, scroll, drag, multi-step sequences), app launching, and demo retrieval. There are no obvious gaps for typical UI automation tasks.

Resources