Skip to main content
Glama
callstack

agent-device

Official
by callstack
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

react-native

Dismiss a visible development error overlay to unblock UI automation. Use this helper to clear the screen before continuing tests; times out after 90 seconds.

Instructions

Run supported React Native automation helpers. Use dismiss-overlay to close a visible development error overlay before continuing normal UI automation. Times out after 90s.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidNoiOS device UDID selector.
debugNoEnable debug diagnostics.
runIdNoLease run identifier.
actionYes
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.
leaseIdNoExisting lease identifier.
sessionNoAgent-device session name.
noRecordNoDo not record this action.
platformNoPlatform selector used to resolve a device.
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.
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.

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. Changed3 schema fields changedv0.20.2
    • addedInput schema / properties / noRecord
      Added value: +{
+  "description": "Do not record this action.",
+  "type": "boolean"
+}
    • 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."
  4. Changed3 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"
+]
    • 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. First observedv0.16.9

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the behavioral burden. It adds a 90s timeout and identifies the action as dismissing the RN dev overlay, which is useful. It does not disclose what happens when no overlay is present, whether the action is disruptive, or what a successful result looks like.

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?

Two sentences convey the tool's scope, the concrete action, the condition for using it, and a timeout. It is front-loaded with the general purpose and specific use, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-action automation tool with a generous schema, the description covers the key trigger and the timeout. However, there is no output schema and no mention of return format, error conditions, or behavior when the overlay is absent, leaving an agent to guess at success/failure semantics.

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 94%, and the schema documents all 17 common parameters with descriptions and enums. The description adds no parameter-specific meaning, but the schema already provides the needed detail for the only action and selectors; baseline 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?

Description identifies the tool as handling React Native automation helpers and specifically names the dismiss-overlay action with its purpose: closing a visible development error overlay. Without inspecting the schema, an agent can infer what invocation achieves. It is not fully distinguished from sibling tools, but its specific use case 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 Guidelines4/5

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

Description states when to use it: after a development error overlay appears, before continuing normal UI automation. It does not name alternative tools or exclusions, but the tool's single action and targeted condition make the usage context reasonably unambiguous.

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