Skip to main content
Glama

install-from-source

Install app builds from URLs, remote source specs, or CI artifacts, targeting iOS, Android, desktop, or TV devices.

Instructions

Install app builds from URLs, remote source specs, or CI artifacts resolved by a remote daemon.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory for command execution.
udidNoiOS device UDID selector.
debugNoEnable debug diagnostics.
runIdNoLease run identifier.
deviceNoDevice name selector.
serialNoAndroid device or Vega VVD serial selector.
sourceYesInstall source object.
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.
noRecordNoDo not record this action.
platformNoPlatform selector used to resolve a device.
stateDirNoAgent-device state directory.
includeCostNoInclude per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.
retainPathsNo
retentionMsNo
deviceTargetNoDevice target form. Maps to the CLI --target flag.
daemonBaseUrlNoRemote daemon base URL.
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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only notes the source resolution by a remote daemon but omits side effects, permissions, or target device impact, which is a significant gap for a mutation tool.

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, front-loaded sentence with zero wasted words. It immediately communicates the action and key source distinctions, making it highly concise and well-structured.

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?

For a tool with 27 parameters, nested objects, and no output schema, this one-line description is insufficient. It lacks context about device targets, remote daemon configuration, expected responses, or operational prerequisites, leaving agents under-informed for complex invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (93%), providing descriptions for most parameters. The description adds value by enriching the required 'source' parameter with concrete types (URLs, remote specs, CI artifacts), which the schema's generic 'Install source object' does not convey.

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 tool installs app builds and specifies the exact source types: URLs, remote source specs, or CI artifacts resolved by a remote daemon. This distinguishes it from sibling tools like 'install' and 'reinstall' by focusing on non-standard sources.

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?

The description implies usage for non-standard build sources via the mention of URLs and remote artifacts, but it offers no explicit guidance on when to use this tool versus the simpler 'install' sibling, nor does it state any exclusions or prerequisites.

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