Skip to main content
Glama

open

Open an app, deep link, URL, or platform surface. Specify platform, device, and optional arguments to launch on iOS, Android, desktop, or TV.

Instructions

Open an app, deep link, URL, or platform surface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionNoAgent-device session name.
platformNoPlatform selector used to resolve a device.
deviceTargetNoDevice target form. Maps to the CLI --target flag.
targetNoAlias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
deviceNoDevice name selector.
udidNoiOS device UDID selector.
serialNoAndroid serial selector.
iosSimulatorDeviceSetNoiOS simulator device-set path used for device resolution.
androidDeviceAllowlistNoAndroid serial allowlist used for device resolution.
daemonBaseUrlNoRemote daemon base URL.
daemonAuthTokenNoRemote daemon auth token.
tenantNoRemote tenant identifier.
runIdNoLease run identifier.
leaseIdNoExisting lease identifier.
cwdNoWorking directory for command execution.
debugNoEnable debug diagnostics.
appNoApp name, bundle id, package, or URL.
urlNoOptional URL passed with an app shell.
surfaceNo
activityNoAndroid activity name.
launchConsoleNoLaunch console mode.
launchArgsNoLaunch arguments forwarded verbatim to the platform launch command.
relaunchNoForce relaunch.
saveScriptNo
noRecordNoDo not record this action.
stateDirNoAgent-device state directory.
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states the basic action, omitting details like error handling, side effects, or required permissions.

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 a single sentence with no wasted words, highly efficient and front-loaded.

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?

Given the tool's 26 parameters and many sibling tools, the description is too brief. It provides no context on parameter relationships, usage patterns, or how to choose between similar tools.

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 coverage is 92%, so baseline is 3. The description adds no additional meaning to the parameters, leaving the agent to rely solely on schema descriptions.

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 tool opens an app, deep link, URL, or platform surface. However, it does not differentiate from sibling tools like 'apps' or 'appstate' which may have overlapping functionality.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No context about prerequisites or typical scenarios is provided.

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/callstack/agent-device'

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