Skip to main content
Glama

open

Open apps, deep links, URLs, or platform surfaces on iOS, Android, desktop, and TV devices.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoApp name, bundle id, package, or URL.
cwdNoWorking directory for command execution.
urlNoOptional URL passed with an app shell.
udidNoiOS device UDID selector.
debugNoEnable debug diagnostics.
runIdNoLease run identifier.
deviceNoDevice name selector.
serialNoAndroid serial selector.
targetNoAlias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
tenantNoRemote tenant identifier.
leaseIdNoExisting lease identifier.
sessionNoAgent-device session name.
surfaceNo
activityNoAndroid activity name.
noRecordNoDo not record this action.
platformNoPlatform selector used to resolve a device.
relaunchNoForce relaunch.
stateDirNoAgent-device state directory.
deviceHubNoUse Xcode Device Hub when surfacing Apple simulators.
launchArgsNoLaunch arguments forwarded verbatim to the platform launch command.
saveScriptNo
includeCostNoInclude per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.
deviceTargetNoDevice target form. Maps to the CLI --target flag.
daemonBaseUrlNoRemote daemon base URL.
launchConsoleNoLaunch console mode.
responseLevelNoResponse verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.
daemonAuthTokenNoRemote daemon auth token.
iosXctestEnvDirNoWritable directory for iOS XCTest runner env overlays.
mcpOutputFormatNoMCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.
iosXctestrunFileNoExternally built iOS XCTest runner .xctestrun artifact path.
iosSimulatorDeviceSetNoiOS simulator device-set path used for device resolution.
androidDeviceAllowlistNoAndroid serial allowlist used for device resolution.
iosXctestDerivedDataPathNoDerived data path for external iOS XCTest runner execution.
Behavior2/5

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

With no annotations, the description must fully disclose behavior, but it only states the action without any side effects, error conditions, or prerequisites. Missing details like whether it launches a new instance or activates existing, permission requirements, or platform-specific behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but under-specified given 33 parameters. It could benefit from a structured breakdown or example usage. Not overly long, but too brief for the complexity.

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 high schema coverage and no output schema, the description lacks details on return values, errors, or edge cases. For a tool with many parameters and no annotations, the description is insufficient to fully understand its behavior.

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 high (94%), so the schema already documents most parameters. The description adds minimal value beyond summarizing the tool's purpose; it doesn't explain parameter interplay or usage patterns. Baseline of 3 is appropriate.

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 apps, deep links, URLs, or platform surfaces. It uses a specific verb and resource, but lacks explicit differentiation from sibling tools like 'click' or 'press'. The term 'platform surface' is slightly vague but overall purpose is clear.

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 is provided on when to use this tool versus alternatives. There are no usage constraints, prerequisites, or explicit comparisons to sibling tools like 'click' or 'launch'.

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