Skip to main content
Glama
verisoft-ai

windows2-mcp

by verisoft-ai

create_session

Destructive

Launch a Windows application and start a new Appium session for UI automation. Supports attaching to running windows or launching new instances.

Instructions

Launch a Windows application and start a new Appium session. Ask the user before calling — confirm they want a new app instance launched.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoExecutable path (e.g. "C:\\Windows\\notepad.exe") or UWP App ID (e.g. "Microsoft.WindowsCalculator_8wekyb3d8bbwe!App") or "Root" to attach to the desktop root. Omit when using appTopLevelWindow to attach to an already-running window.
jdkPathNoPath to the JDK installation used to inject the Java agent (e.g. "C:\\Program Files\\Eclipse Adoptium\\jdk-21"). Required if javaSwing is true and JAVA_HOME is not set.
javaSwingNoEnable Java agent support for automating Java Swing/AWT applications. Injects a JVM agent that exposes Java class names, accessible names, and roles for element finding.
appArgumentsNoCommand-line arguments to pass to the app
dotnetBridgeNoEnable .NET bridge support for automating WinForms/WPF apps with custom-drawn controls (e.g. DevExpress) that expose little or nothing via UIA. Injects a bridge DLL into the target CLR process. Requires appTopLevelWindow — there is no launch-time injection for .NET, only attach to an already-running process.
appWorkingDirNoWorking directory for the app process
shouldCloseAppNoWhether to close the app when delete_session is called
webviewEnabledNoEnable WebView/CDP support for hybrid apps (Edge/Chrome-based embedded webviews)
delayAfterClickNoMilliseconds to wait after each click
implicitTimeoutNoImplicit element wait timeout in milliseconds
delayBeforeClickNoMilliseconds to wait before each click
waitForAppLaunchNoMilliseconds to wait after app launch before interacting
appTopLevelWindowNoNative window handle (decimal or hex string, e.g. "0x001A0B2C") of an already-running window to attach to instead of launching a new app. Use with javaSwing:true to attach the Java agent to an existing Java Swing/AWT window, or with dotnetBridge:true to attach the .NET bridge to an existing WinForms/WPF window.
smoothPointerMoveNoEasing function name for smooth pointer movement
ieDriverServerPathNoAbsolute path to a local IEDriverServer.exe. Overrides the auto-downloaded binary when IE windows are automated. Example: "C:\\WebDriver\\IEDriverServer.exe"
webviewDevtoolsPortNoDevTools remote debugging port the embedded webview is listening on
newSessionCommandTimeoutNoSeconds of inactivity before Appium auto-closes the session (default: 3600). Maps to Appium newCommandTimeout capability.
Behavior3/5

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

The annotation destructiveHint: true already flags the tool as destructive. The description adds 'launch a new app instance' which implies resource consumption and user confirmation, but does not disclose other behavioral traits such as session lifecycle, resource cleanup, or what happens if a session already exists. With annotations present, the description provides adequate but not rich context.

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?

The description is two sentences: the first states the purpose, the second gives a critical usage instruction. It is front-loaded, concise, and every sentence adds value. No unnecessary words.

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?

Despite the rich schema, the description is misleading: it says 'Launch a Windows application' but the schema allows attaching to an existing window via appTopLevelWindow without launching. It also does not explain what the tool returns (e.g., a session ID) or how to use the result with other tools. For a complex tool with 17 parameters and no output schema, this is a significant gap.

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 parameter already has a description. The tool description does not add any additional parameter meaning beyond what is in the schema. The baseline is 3 for high coverage, and the description does not enhance it.

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?

The description clearly states the action: 'Launch a Windows application and start a new Appium session.' This specifies a distinct verb and resource, and the sibling tools (attach_session, delete_session) make it obvious this is for creating a new session, not attaching or deleting.

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?

The description explicitly tells the agent to 'Ask the user before calling — confirm they want a new app instance launched.' This is strong guidance on when to use the tool. However, it does not explicitly contrast with attach_session (e.g., 'use this for launching new apps, attach_session for existing ones').

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/verisoft-ai/windows2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server