Skip to main content
Glama

test

Run one or more replay scripts on real devices including iOS, Android, macOS, Linux, and Apple platforms to automate and verify app behavior.

Instructions

Run one or more replay scripts.

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.
pathsYes
updateNo
backendNo
maestroNo
envNo
failFastNo
timeoutMsNo
retriesNo
recordVideoNo
artifactsDirNo
reportJunitNo
shardAllNo
shardSplitNo
stateDirNoAgent-device state directory.
Behavior2/5

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

No annotations exist, and the description only states the action without revealing side effects, permissions, or whether it is destructive. Lacks essential behavioral context for such a parameter-heavy tool.

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?

Extremely concise but at the expense of completeness. While brevity is positive, more detail is needed for a tool with 30 parameters.

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?

No output schema, high parameter count, and no behavioral details or usage examples. The description is insufficient for the tool's complexity.

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

Parameters2/5

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

Schema coverage is 57%; many parameters lack descriptions. The description adds no additional meaning, leaving the agent to infer usage from parameter names and enum values.

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?

Description clearly states the tool runs replay scripts with a specific verb and resource. However, it does not define what 'replay scripts' are or how they differ from the sibling 'replay' tool.

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 like 'replay', 'batch', or other testing tools. No prerequisites or context 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