Skip to main content
Glama

test

Run replay scripts as a serial test suite. Streams progress and avoids fixed client timeouts.

Instructions

Run one or more replay scripts as a serial test suite Streams progress; no fixed client timeout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNo
udidNoiOS device UDID selector.
debugNoEnable debug diagnostics.
pathsYes
runIdNoLease run identifier.
deviceNoDevice name selector.
serialNoAndroid device or Vega VVD serial selector.
targetNoAlias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
tenantNoRemote tenant identifier.
updateNo
backendNo
leaseIdNoExisting lease identifier.
maestroNo
retriesNo
sessionNoAgent-device session name.
failFastNo
platformNoPlatform selector used to resolve a device.
shardAllNo
bundleUrlNoBundle URL hint inherited by each test session.
metroHostNoMetro/debug host hint inherited by each test session.
metroPortNoMetro/debug port hint inherited by each test session.
timeoutMsNo
shardSplitNo
includeCostNoInclude per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.
recordVideoNo
artifactsDirNo
deviceTargetNoDevice target form. Maps to the CLI --target flag.
responseLevelNoResponse verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.
mcpOutputFormatNoMCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.
androidDeviceAllowlistNoAndroid serial allowlist used for device resolution.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
testsYes
totalYes
failedYes
notRunYes
passedYes
skippedYes
executedYes
failuresYes
durationMsYes
snapshotDiagnosticsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changedv0.20.10
    • removedInput schema / properties / cwd
      Removed value: -{
      -  "description": "Working directory for command execution.",
      -  "type": "string"
      -}
    • removedInput schema / properties / daemonAuthToken
      Removed value: -{
      -  "description": "Remote daemon auth token.",
      -  "type": "string"
      -}
    • removedInput schema / properties / daemonBaseUrl
      Removed value: -{
      -  "description": "Remote daemon base URL.",
      -  "type": "string"
      -}
    • removedInput schema / properties / iosSimulatorDeviceSet
      Removed value: -{
      -  "description": "iOS simulator device-set path used for device resolution.",
      -  "type": "string"
      -}
    • removedInput schema / properties / iosXctestDerivedDataPath
      Removed value: -{
      -  "description": "Derived data path for external iOS XCTest runner execution.",
      -  "type": "string"
      -}
    • removedInput schema / properties / iosXctestEnvDir
      Removed value: -{
      -  "description": "Writable directory for iOS XCTest runner env overlays.",
      -  "type": "string"
      -}
    • removedInput schema / properties / iosXctestrunFile
      Removed value: -{
      -  "description": "Externally built iOS XCTest runner .xctestrun artifact path.",
      -  "type": "string"
      -}
    • removedInput schema / properties / stateDir
      Removed value: -{
      -  "description": "Agent-device state directory.",
      -  "type": "string"
      -}
  2. Changed1 schema field changedv0.20.9
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "apple",
      -  "android",
      -  "vega",
      -  "linux",
      -  "web",
      -  "ios",
      -  "macos"
      -]New value: +[
      +  "apple",
      +  "android",
      +  "harmonyos",
      +  "vega",
      +  "linux",
      +  "web",
      +  "ios",
      +  "macos"
      +]
  3. Changed6 schema fields changedv0.20.2
    • addedInput schema / properties / bundleUrl
      Added value: +{
      +  "description": "Bundle URL hint inherited by each test session.",
      +  "type": "string"
      +}
    • addedInput schema / properties / metroHost
      Added value: +{
      +  "description": "Metro/debug host hint inherited by each test session.",
      +  "type": "string"
      +}
    • addedInput schema / properties / metroPort
      Added value: +{
      +  "description": "Metro/debug port hint inherited by each test session.",
      +  "type": "integer"
      +}
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "apple",
      -  "android",
      -  "linux",
      -  "web",
      -  "ios",
      -  "macos"
      -]New value: +[
      +  "apple",
      +  "android",
      +  "vega",
      +  "linux",
      +  "web",
      +  "ios",
      +  "macos"
      +]
    • changedInput schema / properties / serial / description
      Previous value: -"Android serial selector."New value: +"Android device or Vega VVD serial selector."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "durationMs": {
      +      "type": "number"
      +    },
      +    "executed": {
      +      "type": "number"
      +    },
      +    "failed": {
      +      "type": "number"
      +    },
      +    "failures": {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "notRun": {
      +      "type": "number"
      +    },
      +    "passed": {
      +      "type": "number"
      +    },
      +    "skipped": {
      +      "type": "number"
      +    },
      +    "snapshotDiagnostics": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "tests": {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "executed",
      +    "passed",
      +    "failed",
      +    "skipped",
      +    "notRun",
      +    "durationMs",
      +    "failures",
      +    "tests"
      +  ],
      +  "type": "object"
      +}
  4. Changed4 schema fields changedv0.17.11
    • addedInput schema / properties / includeCost
      Added value: +{
      +  "description": "Include per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "ios",
      -  "macos",
      -  "android",
      -  "linux",
      -  "web",
      -  "apple"
      -]New value: +[
      +  "apple",
      +  "android",
      +  "linux",
      +  "web",
      +  "ios",
      +  "macos"
      +]
    • removedInput schema / properties / reportJunit
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / responseLevel
      Added value: +{
      +  "description": "Response verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.",
      +  "enum": [
      +    "digest",
      +    "default",
      +    "full"
      +  ],
      +  "type": "string"
      +}
  5. Changed1 schema field changedv0.17.7
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "ios",
      -  "macos",
      -  "android",
      -  "linux",
      -  "apple"
      -]New value: +[
      +  "ios",
      +  "macos",
      +  "android",
      +  "linux",
      +  "web",
      +  "apple"
      +]
  6. Changed5 schema fields changedv0.17.6
    • addedInput schema / properties / iosXctestDerivedDataPath
      Added value: +{
      +  "description": "Derived data path for external iOS XCTest runner execution.",
      +  "type": "string"
      +}
    • addedInput schema / properties / iosXctestEnvDir
      Added value: +{
      +  "description": "Writable directory for iOS XCTest runner env overlays.",
      +  "type": "string"
      +}
    • addedInput schema / properties / iosXctestrunFile
      Added value: +{
      +  "description": "Externally built iOS XCTest runner .xctestrun artifact path.",
      +  "type": "string"
      +}
    • addedInput schema / properties / mcpOutputFormat
      Added value: +{
      +  "description": "MCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.",
      +  "enum": [
      +    "optimized",
      +    "json"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "ios",
      -  "android",
      -  "macos",
      -  "linux",
      -  "apple"
      -]New value: +[
      +  "ios",
      +  "macos",
      +  "android",
      +  "linux",
      +  "apple"
      +]
  7. Changed3 schema fields changedv0.17.1
    • addedInput schema / properties / recordVideo
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / shardAll
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / shardSplit
      Added value: +{
      +  "type": "integer"
      +}
  8. First observedv0.16.9

TDQS

B3.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses two useful behavioral traits: progress is streamed and there is no fixed client timeout. This goes beyond the schema and helps an agent understand the tool may be long-running. It does not address failure behavior or resource implications, but the core behavioral traits are present.

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

Conciseness4/5

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

The description is one sentence with no filler and front-loads the core action. The structure is slightly awkward—'suite Streams progress' reads like a missing sentence break—but it remains compact and information-dense.

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?

This is a high-complexity tool with 30 parameters, no annotations, and only partial schema coverage, yet the description provides only two behavioral facts: serial execution and streaming/no-timeout. Important context such as when to use this vs replay or batch, how sharding works, or what failure modes exist is missing. The output schema covers return shape, but invocation context is still under-specified.

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?

With 30 parameters and only 60% schema description coverage, the description adds almost no parameter-level meaning. It only implies that 'paths' are the replay scripts via 'one or more replay scripts.' Many parameters such as retries, failFast, shardAll, shardSplit, timeoutMs, and recordVideo are left without description in either the schema or the tool description.

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 states a specific verb and resource: 'Run one or more replay scripts as a serial test suite.' This makes the core purpose clear. However, it does not distinguish this tool from siblings like 'replay' or 'batch', so an agent must infer the differentiator from 'serial test suite.'

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 phrase 'as a serial test suite' implies this tool is for running replay scripts in sequence, which gives some usage context. But there is no explicit guidance about when to choose this over 'replay' or 'batch', and no stated exclusions or alternatives.

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

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